[00:06:24] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_seaboard-tangent-binary" from c62dd9d42bd87964a131adc688d0c70f63cc4cac: ajwong at chromium dot org <ajwong at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[00:09:28] <crosbot> tree became 'Tree is closed (achuith investigating tegra2_seaboard-binary failure KNOWN FAILURES: alex-binary 6056? mario-canary 6056? zgb-canary 16651 stumpy-canary 20305 x86 pineview full 20323)'
[00:12:52] *** katier has quit IRC
[00:17:08] <achuith> hmm, enter_chroot failed looks like
[00:25:50] *** nick761 has quit IRC
[00:26:20] *** nick761 has joined #chromium-os
[00:35:14] *** nick761 has quit IRC
[00:35:22] <achuith> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/tegra2_seaboard-tangent-binary/builds/1019/steps/cbuildbot/logs/stdio
[00:35:51] *** nick761 has joined #chromium-os
[00:37:08] <achuith> clobber and retrying
[00:39:48] <gauravsh> crosbot: sheriffs?
[00:39:48] <crosbot> gauravsh: sheriffs: achuith, grundler, kliegs
[00:40:00] <achuith> hi
[00:40:27] <gauravsh> i need to push a change to a script that is not used anywhere except the production signer
[00:40:32] <gauravsh> may I submit?
[00:40:57] <achuith> go for it
[00:42:15] <gauravsh> thanks
[00:50:22] *** mbolohan has joined #chromium-os
[00:51:20] *** mbolohan has quit IRC
[00:52:37] *** mbolohan has joined #chromium-os
[00:52:40] *** mbolohan has quit IRC
[00:53:09] *** mbolohan has joined #chromium-os
[00:57:58] <adlr> davidjames and i just pushed CLs to add logs to the timingout VM tests
[00:58:05] <adlr> which seem to be dying in image_to_live
[01:01:25] <achuith> ok
[01:01:36] *** nick761 has quit IRC
[01:09:56] <grundler> achuith: note that the external builders are still happy with tegra2 builds
[01:10:33] <achuith> grundler: what do you suggest?
[01:11:08] <achuith> grundler: we're pretty close to seeing if enter_chroot fails again
[01:11:17] <grundler> achuith: look at the failure logs with that in mind - nothing special
[01:11:36] <achuith> grundler: ok
[01:13:01] <grundler> oic. this failed right after I took off to my 3pm meeting
[01:13:13] <achuith> grundler: yup
[01:13:31] <achuith> I'm assuming it's some flake with enter_chroot
[01:13:38] <achuith> but there're no bugs on this
[01:13:51] <grundler> chmod: cannot access `/b/cbuild/arm-tegra2_seaboard-tangent-private-bin/chroot/var/lock': No such file or directory
[01:14:00] <grundler> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/tegra2_seaboard-tangent-binary/builds/1019/steps/cbuildbot/logs/stdio
[01:14:21] <grundler>  ** Start Stage BuildBoard - 15:02:57
[01:14:28] <achuith> yup
[01:14:41] <grundler> that's the failure you found earlier?
[01:15:53] <achuith> yes
[01:16:19] <achuith> Failed the same way on rebuild
[01:16:23] <achuith> trying a clobber build now
[01:16:34] <grundler> yes - I was just about suggest a clobber
[01:16:45] <grundler> # (Sep 21 13:10) rev=[??] exception #1018: exception cbuildbot failed CleanUp
[01:16:54] <grundler> was the beginning of the problems for that builder
[01:16:59] <grundler> (my guess)
[01:17:28] *** Solet has quit IRC
[01:18:09] <achuith> ugh, that was my fault
[01:18:18] <grundler> ?
[01:18:31] <achuith> the exception, I forced a halt on that builder
[01:18:49] <achuith> I'm tempted to reopen the tree
[01:18:59] <achuith> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/tegra2_seaboard-tangent-binary/builds/1021/steps/cbuildbot/logs/stdio
[01:19:05] <achuith> It looks like it's building ok
[01:19:12] <grundler> ok.
[01:20:22] <crosbot> tree became 'Tree is open (achuith investigating tegra2_seaboard-binary failure KNOWN FAILURES: alex-binary 6056? mario-canary 6056? zgb-canary 16651 stumpy-canary 20305 x86 pineview full 20323)'
[01:27:48] *** ojn has quit IRC
[01:29:53] *** nick761 has joined #chromium-os
[01:35:27] *** ojn has joined #chromium-os
[01:35:27] *** ChanServ sets mode: +v ojn
[01:36:25] *** Solet has joined #chromium-os
[01:36:34] <ojn> Cool, freenode servers are actually available via ipv6.
[01:37:47] <cmasone> how do I know if the commit queue is enabled for my repo?  If there's still a submit button, does that mean no CQ?
[01:43:29] <grundler> Running ['/b/cbuild/x86-alex-private-bin/src/scripts/sdk_lib/enter_chroot.sh', '--chroot', '/b/cbuild/x86-alex-private-bin/chroot', '--', 'bin/cros_make_image_bootable', '/home/chrome-bot/trunk/src/scripts/latest_download', 'chromiumos_test_image.bin', '--force_developer_mode'] failed!
[01:43:39] <grundler> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-alex-binary/builds/1454/steps/VMTest/logs/stdio
[01:46:56] <achuith> hmm
[01:47:06] <achuith> cros_make_image_bootable failed?
[01:47:13] <grundler> I'm thinking that's a dup of 6056 maybe
[01:47:21] <grundler> erm, 6026
[01:47:57] <achuith> http://code.google.com/p/chromium-os/issues/detail?id=6026
[01:47:59] <achuith> That doesn't seem rigt
[01:49:25] <grundler> yeah, it's probably not
[02:00:35] *** katier has joined #chromium-os
[02:00:35] *** ChanServ sets mode: +v katier
[02:02:37] *** wfrichar has quit IRC
[02:05:00] *** lipsinV2 has joined #chromium-os
[02:14:07] <crosbot> tree became 'Tree is open (KNOWN FAILURES: alex-binary 6056? mario-canary 6056? zgb-canary 16651 stumpy-canary 20305 x86 pineview full 20323)'
[02:14:59] *** achuith has quit IRC
[02:19:45] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot_master" on "TOT Pre-Flight Queue" from c44a75491e5201df2cfaf83238cdc825df1d1e20: bradnelson at google dot com <bradnelson at google dot com@0039d316-1c4b-4281-b951-d872f2087c98>)'
[02:22:44] <cmasone> ffffffffffffffuuuuuuuuuuuuuuuuuuuuuuuuu
[02:26:12] <grundler> uh...I lost my co-sheriff. :(
[02:27:36] *** sadrul has joined #chromium-os
[02:27:36] *** ChanServ sets mode: +v sadrul
[02:28:33] <grundler> suite_Smoke/security_ProfilePermissions.login      FAIL
[02:29:35] <grundler> suite_Smoke/desktopui_WindowManagerFocusNewWindows FAIL
[02:31:06] *** achuith has joined #chromium-os
[02:31:45] *** achuith has joined #chromium-os
[02:32:02] <crosbot> tree became 'Tree is closed (achuith investigating KNOWN FAILURES: alex-binary 6056? mario-canary 6056? zgb-canary 16651 stumpy-canary 20305 x86 pineview full 20323)'
[02:33:24] <grundler> achuith, I'm seeing some test failures...anything else I'm missing?
[02:34:38] <grundler> cmasone: any chance this error is related to previous change to use NF_NAT for DNS proxy?
[02:34:41] <nirnimesh> Have any of the sheriffs seen the 'Chrome did not reopen the testing channel after login as guest' test failure today?
[02:34:41] <grundler> 09/21 17:08:22 ERROR|site_utils:0065| Timed out waiting to revert DNS.
[02:35:02] <achuith> nirnimesh: no, not today
[02:35:09] <grundler> nirnimesh: I don't think I have either
[02:35:22] <achuith> grundler: do you know why tests are failing?
[02:35:52] <grundler> achuith: not off hand. My guess is we need to look at recent commits
[02:36:03] <grundler> and consider reverting something.
[02:36:12] <achuith> grundler: so this looksl ike a real failure, right?
[02:38:48] <grundler> so far, yeah
[02:40:14] <grundler> achuith: http://chromeos-botmaster.mtv.corp.google.com:8026/builders/TOT%20Pre-Flight%20Queue/builds/5669/steps/cbuildbot/logs/stdio
[02:40:22] <grundler> seems to have the first TOT failure.
[02:41:08] <achuith> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/TOT%20Pre-Flight%20Queue/builds/5669/steps/VMTest/logs/stdio
[02:41:38] <grundler> yeah, same thing I think
[02:42:07] <cmasone> grundler: the ToT PFQ is just 19005 again
[02:42:15] <grundler> ah...cmasone submitted something...we should just revert that :P
[02:42:37] * grundler looks at 19005
[02:42:40] <grundler> (again)
[02:42:47] <cmasone> it's not introduced by my changes, it's just that my changes have still not worked around whatever underlying race there is
[02:43:05] <achuith> heh
[02:43:06] <grundler> cmasone: just teasing...easy target :)
[02:44:36] <cmasone> now, the x86-generic PFQ failure that just happened, that
[02:44:39] <cmasone> is not me
[02:47:19] <achuith> http://gerrit.chromium.org/gerrit/#change,8041
[02:47:21] <achuith> ?
[02:47:54] <grundler> x86-generic PFQ failure is crosbug/20323 maybe?
[02:48:43] <grundler> 09/21 17:19:49 ERROR|logging_ma:0560| [3044:3044:0921/171949:249831099:ERROR:proxy_launcher.cc(562)] Failed to ConnectToRunningBrowser
[02:48:51] <grundler> http://build.chromium.org/p/chromiumos/builders/x86%20generic%20PFQ/builds/956/steps/VMTest/logs/stdio
[02:49:05] <achuith> We're not seeing the WaitForInitialLoad error message, right?
[02:49:15] <grundler> 09/21 17:33:03 ERROR|logging_ma:0560| [13529:13529:0921/173303:1043708604:ERROR:proxy_launcher.cc(109)] WaitForInitialLoads failed.
[02:49:18] <grundler> we are
[02:49:38] <grundler> lots of them in that log file
[02:50:27] <achuith> are we looking at different failures?
[02:50:46] <achuith> I was looking at http://chromeos-botmaster.mtv.corp.google.com:8026/builders/TOT%20Pre-Flight%20Queue/builds/5669/steps/VMTest/logs/stdio
[02:50:49] <grundler> achuith: there are two failures
[02:50:54] <achuith> ok
[02:51:06] <cmasone> achuith: that's the one that I was talking to grant about aboce
[02:51:07] <grundler> right. x86-generic and TOT PFQ both failed
[02:51:08] <cmasone> above
[02:53:21] <achuith> looks like TOT PFQ built?
[02:53:54] <grundler> grrh...Sites editor barfed.
[02:54:58] <achuith> so failures are just x86-mario canary and x86-alex-binary?
[02:55:14] <grundler> yeah, I think so.
[02:55:41] <achuith> which one are you looking at?
[02:57:02] <grundler> I've concluded both look like existing failures: TOT PFQ is 19005 (per cmasone) and x86-generic PFQ looks like 20323
[02:57:22] <grundler> oh...you meant the canary and alex-binary?
[02:57:25] <achuith> yes
[02:57:34] <achuith> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-mario%20canary/builds/1034/steps/VMTest/logs/stdio
[02:57:34] <grundler> sorry...
[02:57:43] <achuith> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-alex-binary/builds/1454/steps/VMTest/logs/stdio
[02:57:59] <grundler> I'll take a look at alex-binary but then have to leave.
[02:58:45] <grundler> uhm...x86-alex-binary seems to have built fine in the last round.
[02:58:46] <achuith> alex binary has the same enter_chroot failure
[02:58:59] <grundler> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-alex-binary
[02:59:07] <achuith> you're right
[02:59:17] <grundler> 1454 failed. 1455 succeeded.
[02:59:18] <achuith> ok, it just righted itself
[02:59:20] <achuith> but it did fail
[02:59:27] <grundler> yes, it definitely failed.
[02:59:29] <achuith> with the enter_chroot problem with make_image_bootable
[02:59:46] <grundler> ISTR looking at 1454 earlier too
[02:59:50] <grundler> yes
[02:59:59] <grundler> ok. time to flee. :)
[03:00:02] <achuith> cros_build_lib.RunCommandException: Command "['cros_sdk', '--', 'bin/cros_make_image_bootable', '/home/chrome-bot/trunk/src/scripts/latest_download', 'chromiumos_test_image.bin', '--force_developer_mode']" failed.
[03:00:23] <achuith> k
[03:00:41] <grundler> I'll be back early tomorrow (8AM-ish)
[03:00:49] *** grundler has quit IRC
[03:02:45] <crosbot> tree became 'Tree is open (KNOWN FAILURES: alex-binary 6056? mario-canary 6056? zgb-canary 16651 stumpy-canary 20305 x86 pineview full 20323)'
[03:08:11] *** saintlou has quit IRC
[03:18:53] *** chocobo__ has quit IRC
[03:32:04] *** achuith has quit IRC
[04:00:17] *** mkunze has quit IRC
[04:03:07] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "x86 pineview full" from e622f1159557b53bac98d0b7b3a482f2a3cdac8f: Gaurav Shah <gauravsh at chromium dot org>, Mandeep Singh Baines <msb at chromium dot org>)'
[04:07:59] <crosbot> tree became 'Tree is open (KNOWN FAILURES: alex-binary 6056? mario-canary 6056? zgb-canary 16651 stumpy-canary 20305 x86 pineview full 20323)'
[04:26:08] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot_master" on "TOT Pre-Flight Queue" from 2fc32da1d5ce09de63658853a0972a32cca5e46c: akalin at chromium dot org <akalin at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[04:55:04] <crosbot> tree became 'Tree is open (TOT Pre-Flight Queue -> crosbug.com/20323, VMTest part cycled green)'
[04:56:00] *** dalecurtis has quit IRC
[04:56:33] *** dennisjeffrey has quit IRC
[05:27:36] *** jochen__ has quit IRC
[05:27:41] *** jochen__ has joined #chromium-os
[05:27:41] *** ChanServ sets mode: +v jochen__
[05:44:08] *** Ruetobas has quit IRC
[05:47:31] *** Ruetobas has joined #chromium-os
[05:53:51] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "x86 generic full" from e8aec371654480a9173913aaa5fead65a1304baa: Mike Frysinger <vapier at chromium dot org>, Paul Stewart <pstew at chromium dot org>, Simon Que <sque at chromium dot org>)'
[05:57:15] *** rkc has joined #chromium-os
[05:57:15] *** ChanServ sets mode: +v rkc
[06:03:11] *** Justasic_ has quit IRC
[06:04:40] <redpig> crosbot: sheriffs?
[06:04:40] <crosbot> redpig: sheriffs: achuith, grundler, kliegs
[06:04:56] <redpig> any sheriffs actually around?
[06:05:11] <redpig> guessing this failure is the dns time out cmasone's change in pfq should help with
[06:11:52] *** Justasic has joined #chromium-os
[06:12:12] *** TW1920 has joined #chromium-os
[06:12:29] <redpig> hrm
[06:24:04] <srao> i'm not sure it's the dns time out
[06:24:12] <srao> it looks like the network connection just went down completely
[06:28:28] <srao> looks sorta like 20514
[06:30:51] <srao> I'll reopen
[06:34:29] <crosbot> tree became 'Tree is open(crosbug.com/20323 network died)'
[06:43:35] *** flackr has quit IRC
[06:44:28] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot_master" on "TOT Pre-Flight Queue" from 67bfb83fbdd401bba2cfdbe330edebf2b3105a6f: yzshen at chromium dot org <yzshen at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[06:47:26] <srao> doh
[06:47:57] *** rsleevi has quit IRC
[06:49:33] *** rsleevi has joined #chromium-os
[06:57:03] *** dots has quit IRC
[06:57:04] *** Hexxeh has quit IRC
[06:57:10] *** reveman has quit IRC
[07:11:21] <crosbot> tree became 'Tree is open (crosbug.com/20323)'
[07:21:31] *** rkc has quit IRC
[07:50:07] *** zmedico has quit IRC
[07:59:32] *** silverroots has joined #chromium-os
[08:07:08] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "x86-zgb-binary" from 5afcbf4f9b2e49c8d84bacc585f051bb472b8501: sail at chromium dot org <sail at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[08:37:20] *** patcito has quit IRC
[08:37:21] *** silverroots has quit IRC
[08:39:52] *** silverroots has joined #chromium-os
[08:45:38] *** sadrul has quit IRC
[08:45:47] *** vmil86 has joined #chromium-os
[08:47:11] *** zmedico has joined #chromium-os
[09:01:43] *** sadrul has joined #chromium-os
[09:16:42] *** akrpic77 has joined #chromium-os
[09:16:46] <akrpic77> hello
[09:19:25] <akrpic77> i have special HID device, which i would need to capture data, and send to web server, at the time when browser is at that web server.
[09:20:37] <akrpic77> what would i need to do? NaCL is out because of sandboxing. Is there another way to access IO ? i'm willing to write browser extension, or whatever is needed.
[09:21:13] *** Styx has joined #chromium-os
[09:29:13] *** Clark008 has quit IRC
[09:29:50] <akrpic77> hmm
[09:42:43] <akrpic77> to rephrase. idea is to run 3d world in browser. i want to control avatar movement that with a hid device (e.g. joystick). what are my options to do that in chrome os ?
[09:56:25] *** reveman has joined #chromium-os
[09:56:25] *** silverroots has quit IRC
[09:58:45] *** dots has joined #chromium-os
[10:06:14] *** pastarmovj has joined #chromium-os
[10:09:56] *** Hexxeh has joined #chromium-os
[10:56:07] *** achuith has joined #chromium-os
[10:56:07] *** ChanServ sets mode: +v achuith
[11:02:11] *** achuith has quit IRC
[11:04:44] *** mkunze has joined #chromium-os
[11:19:54] *** mkunze has quit IRC
[11:33:15] *** TW1920 has quit IRC
[11:34:26] *** TW1920 has joined #chromium-os
[11:47:03] *** moes has joined #chromium-os
[12:17:30] *** moes has quit IRC
[12:50:11] *** vmil86 has quit IRC
[12:54:42] *** vmil86 has joined #chromium-os
[13:23:29] <crosbot> tree became 'Tree is open (x86-zgb-binary -> crosbug.com/20323 ?)'
[13:27:35] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_asymptote-binary" from 6a99e0c231250fad8da4d56e3e552c555bb70fbe: dmazzoni at chromium dot org <dmazzoni at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[13:56:14] *** hashimoto has left #chromium-os
[14:29:07] *** Clark008 has joined #chromium-os
[15:39:02] *** flackr has joined #chromium-os
[15:53:29] <kliegs> investigating redness
[15:53:40] *** randomubuntuguy has joined #chromium-os
[15:54:49] *** gdv has joined #chromium-os
[15:57:06] <crosbot> tree became 'Tree is closed (multiple failures, kliegs investigating)'
[16:02:04] *** gdv has quit IRC
[16:05:00] *** rharrison_chrome has joined #chromium-os
[16:05:01] *** ChanServ sets mode: +v rharrison_chrome
[16:07:18] <kliegs> So far all are crosbug.com/20323 it seems.
[16:09:09] *** bshe has joined #chromium-os
[16:09:09] *** ChanServ sets mode: +v bshe
[16:12:54] <kliegs> I'm going to leave the tree closed as testing has degraded to the point of being trivial
[16:13:21] *** wfrichar has joined #chromium-os
[16:13:22] *** ChanServ sets mode: +v wfrichar
[16:14:26] <kliegs> nirnimesh, xiyuan: ping - saw both of you had done some investigating of the bug
[16:24:50] *** akrpic77 has quit IRC
[16:28:58] *** Adys has quit IRC
[16:30:29] *** magn3ts has quit IRC
[16:30:29] *** magn3ts has joined #chromium-os
[16:35:00] <crosbot> tree became 'Tree is closed (crosbug.com/20323 - leaving closed as testing is fairly useless.  have pinged people working on fix for status -kliegs)'
[16:44:57] *** Solet has quit IRC
[16:55:55] *** sadrul has quit IRC
[16:57:41] *** sadrul has joined #chromium-os
[16:57:42] *** ChanServ sets mode: +v sadrul
[17:04:15] *** grundler has joined #chromium-os
[17:04:16] *** ChanServ sets mode: +v grundler
[17:05:49] *** petermayo has joined #chromium-os
[17:05:50] *** ChanServ sets mode: +v petermayo
[17:07:32] * grundler is heading to get breakfast and can then start sheriff duty for today :)
[17:08:36] *** flackr has quit IRC
[17:15:18] *** flackr has joined #chromium-os
[17:26:31] <kliegs> grundler: when back need you to track down zel or xiyuan re: crosbug.com/20323
[17:27:21] <cmasone> kliegs: they won't be here for a while yet.  Also, they'll first ask you is "what  version of chrome?  I landed some fixes yesterday." as I posted in the byg
[17:27:42] <kliegs> cmasone: thanks - getting that info now.
[17:27:58] <cmasone> kliegs: I also put that info in the byg
[17:28:00] <cmasone> bug
[17:28:24] <kliegs> cmasone: which bug - didn't see that info from you?
[17:28:35] <kliegs> oh. just updated
[17:28:59] <kliegs> checking now
[17:29:09] <cmasone> 45 mins ago, yes
[17:30:27] <kliegs> ok. seeing the wrong version
[17:30:33] <kliegs> on the reds
[17:31:42] <kliegs> is the asan builder a closer or advisory?
[17:33:02] <cmasone> the "important" link at the top shows you a view of all the tree-closer bot
[17:33:03] <cmasone> s
[17:33:43] <kliegs> ok cool.  wasn't sure that was being kept current. filing bug for asan then and not worrying about it
[17:34:07] <kliegs> going to reopen tree then as binaries have mostly gone green.
[17:34:59] <crosbot> tree became 'Tree is open (crosbug.com/20323 looks resolved, full builds still need to run.  tangent/symptote redness has fix incoming but may be red until tomorrow)'
[17:35:34] *** mascondante has joined #chromium-os
[17:37:26] *** corburn has joined #chromium-os
[17:37:50] *** corburn has quit IRC
[17:39:05] <grundler> kliegs: do I still need to find zel or xiyuan? (checking 20323 bug now)
[17:39:13] <kliegs> grundler: don't believe so
[17:39:17] <grundler> 'k
[17:39:32] <kliegs> it looks like it was just latency on the chrome change getting through the system
[17:40:23] <grundler> ok - that's always been kind of a pain point. :/
[17:40:57] <grundler> kliegs: btw, I've been keeping notes on "tree-closure-postmortems" page (20110921)
[17:41:04] <grundler> feel free to add your own.
[17:41:17] <kliegs> grundler: already have a 20110922 - trying to keep similar to your format
[17:41:34] <cmasone> it's not so much latency.  We rolled chrome, and then nothing ever kicked off the full builds again, because nothing ever kicked off the PFQs
[17:41:54] <cmasone> The Chrome PFQs finished at about 4AM pacific
[17:42:07] <cmasone> the PFQs haven't run since 11 last night
[17:42:15] <kliegs> cmasone: ahh - sorry.  thought it was lag in rolling chrome.  i'll kick off the remaining red bots
[17:42:58] <grundler> kliegs: oh! :)  I'm going to rewrite 0921 to make it more like a summary than raw notes
[17:43:24] <cmasone> that is an infrastructure bug, possibly related to crbug.com/92109
[17:45:10] <kliegs> grundler: I think either works - mainly just making a good way to see what's happened
[17:45:58] * grundler nods
[17:46:28] <grundler> I just suspect after a few months...there will be a "forest" of such reports and we won't be able to identify trends.
[17:46:56] <grundler> ie probably don't want daily snapshots there.
[17:47:09] *** Adys has joined #chromium-os
[17:47:18] <kliegs> grundler: hmm.  good point.  like that tree could be used for major items that require deep post mortems
[17:47:22] <kliegs> as opposed to daily log.
[17:47:32] * grundler shrugs -- need to start with something
[17:47:36] <kliegs> last rotation we used a google doc. a bit easier to update
[17:47:56] <kliegs> i was viewing this as more useful for the sheriffs coming in tomorrow to help them get started
[17:48:03] <grundler> yeah, should probably post a link to a shared google doc for each week or something
[17:49:55] <grundler> anyway, folks interested in post mortems can reorganize this as they see fit. :)
[17:50:16] <kliegs> we could always make a separate doc for anything major. and then add that as a link on the above page called out
[17:50:26] <kliegs> putting it all on the sites page is nice for easy discoverability
[17:50:41] <grundler> yes, discoverability is way better on sites.
[17:52:49] *** rosso_ has joined #chromium-os
[17:56:22] <njw> Can anyone enlighten me as to the distinction between the autotest-deps ebuild and the individual autotest-deps-$FOO ebuilds? In particular, if I'm adding a couple of deps, do I want to add them to the former or create new individual builds?
[17:56:31] *** patcito has joined #chromium-os
[17:56:55] <kliegs> njw: I think the convention is add them to the most specific spot
[17:57:14] <kliegs> so if only an individual set of tests use add it to -$FOO, if its more generic to autotests in general move it up
[17:57:23] <kliegs> (but this is just my supposition - not an expert on autotest)
[17:57:33] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "stumpy-binary" from beb2f0136e4773f59730a304aa0a5fbed52015e3: _third_party_ at chromium dot org)'
[17:57:41] <kliegs> grundler: dang. investigating
[17:57:42] <cmasone> njw: use autotest-deps unless there is a compelling reason not to
[17:58:14] <cmasone> kliegs: per OOB communication with nkostylev, chrome 889 may have missed Zel's latest fix by a rev or two :-(
[17:58:30] <kliegs> cmasone: well, that explains the error
[17:58:35] <njw> works for me, thanks.
[17:58:46] *** saintlou has joined #chromium-os
[17:58:46] *** ChanServ sets mode: +v saintlou
[17:58:49] <cmasone> njw: compelling reasons may include "wow, this would make all of the autotests start building only after chrome builds!"
[17:58:53] <kliegs> its the same error as we saw. let me go see what 889 is actually building
[17:59:14] <cmasone> kliegs: nkostylev says zel's fix is 102209
[17:59:31] <kliegs> cmasone: zel confirms that - have him on chat
[18:00:54] <grundler> ugh. This is another case of "Kill Button needed" for a known bug (with fix committed) in chrome build pulled into ChromeOS.
[18:02:49] <kliegs> grundler: yah.
[18:03:06] <cmasone> kliegs: might be worth nagging eblake or someone to cut us a chrome buildspec early?
[18:03:46] <kliegs> cmasone: agreed.   eblake can just do that and then the chrome pfq's rev it automatically to stable?
[18:04:03] *** lipsinV2 has quit IRC
[18:04:04] <kliegs> cmasone: only other thing I can think of was checking in mask option to mask in one of the current unstables
[18:04:11] <cmasone> kliegs: yes, though "just do that" is apparently a bit complicated :-)
[18:04:20] <cmasone> kliegs: but once done, it will just progress through automatically
[18:04:21] <kliegs> cmasone: always easier to say than do. i'll ping him
[18:04:38] <kliegs> going to reopen tree, however. unless objections
[18:05:00] <cmasone> kliegs: the issue with masking in an unstable is that we cannot build Google Chrome without one of these buildspecs, so the internal bots will all fail
[18:05:33] <kliegs> ahh.  ok
[18:07:32] <crosbot> tree became 'Tree is open (crosbug.com/20323 missed 889 by 2 revisions so will continue to show up.  looking into creating new chrome buildspec to rev chrome version)'
[18:07:43] <grundler> no objections from me about re-opening the tree.
[18:08:07] <grundler> it would be awesome if you could get the chromium build spec rev'd
[18:09:07] <kliegs> grundler: pinged eblake on chat - no response.  marked as away so might not be in yet
[18:09:14] <kliegs> can you wander by his desk while I go bring back some food?
[18:09:57] <grundler> sure :)
[18:10:14] <grundler> oh... this worked: http://chromium-status.appspot.com/cq
[18:10:30] * grundler can see who has pending changes into chrome. :)
[18:14:48] <kliegs> grundler: rofl
[18:15:13] <grundler> too early for most of that group apperently.
[18:15:23] <grundler> 3-4 people in that section of the building
[18:18:05] <kliegs> grundler: ok. getting some food.  hopefully eblake gets in and can assist
[18:18:13] *** BThompson has quit IRC
[18:18:22] <grundler> kliegs: I'll keep checking every 10-15 minutes :)
[18:18:37] <grundler> maybe I could expense some X10 webcams?
[18:19:18] *** mkunze has joined #chromium-os
[18:19:19] <grundler> or just drop a chromebook running a "special build" near his desk...we have plenty of protos and they run 10+ hours :)
[18:19:54] <grundler> bet it would run 24+h if the display is turned off :)
[18:21:47] <grundler> gotta run an errand...bbiab
[18:23:08] *** BThompson has joined #chromium-os
[18:23:08] *** ChanServ sets mode: +v BThompson
[18:34:35] <kliegs> grundler: back
[18:34:57] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "lumpy-binary" from 4a19be92d9eb20b1619dcf27b7afd3c0da9c4a10: tfarina at chromium dot org <tfarina at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[18:35:05] <kliegs> darg
[18:38:01] <crosbot> tree became 'Tree is open (crosbug.com/20323 missed 889 by 2 revisions so will continue to show up.  looking into creating new chrome buildspec to rev chrome version)'
[18:54:45] *** dennisjeffrey has joined #chromium-os
[18:54:45] *** ChanServ sets mode: +v dennisjeffrey
[19:01:42] <kliegs> grundler, cmasone: http://codereview.chromium.org/7994006/ should be getting us a new buildspec.  eblake just created
[19:03:26] *** rbyers_ has joined #chromium-os
[19:03:55] *** Solet has joined #chromium-os
[19:04:13] *** saintlou has quit IRC
[19:04:56] *** rosso_ has quit IRC
[19:05:52] *** saintlou has joined #chromium-os
[19:05:52] *** ChanServ sets mode: +v saintlou
[19:06:37] <kliegs> need to step away for quick meeting.  back soon - change should hopefully roll through from eblake to get new chrome rev'd
[19:17:00] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot_master" on "x86 generic PFQ" from c2a8f8b5d56157355034375dae1b29df78e1d357: Nathan Williams <njw at chromium dot org>)'
[19:17:23] <njw> Bother.
[19:19:50] <njw> er, that doesn't look like me. Is this one of the issues that's been ongoing today?
[19:24:17] * grundler is looking
[19:25:30] <crosbot> tree became 'Tree is closed (grundler investigating ; "x86 generic PFQ" failure)'
[19:27:13] <grundler> http://build.chromium.org/p/chromiumos/builders/x86%20generic%20PFQ/builds/963/steps/VMTest/logs/stdio
[19:27:21] <grundler> yeah, looks like previous failures :(
[19:28:10] <grundler> "WaitForInitialLoads failed." + "Failed to ConnectToRunningBrowser"
[19:32:40] <crosbot> tree became 'Tree is open ( http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[19:34:18] * grundler goes to find eblake...see if he needs a reviewer/approver for buildspec rev
[19:41:06] <grundler> hrm. not at his desk.
[19:43:28] <grundler> ugh. zel is listed as reviewer...can someone prod zel to dance his part? :)
[19:44:10] <grundler> doh. TBR  - so it's already committed.
[19:49:49] *** dalecurtis has joined #chromium-os
[19:55:27] *** arun_ has quit IRC
[19:55:40] *** solar_ is now known as solar
[20:04:16] *** achuith has joined #chromium-os
[20:04:17] *** ChanServ sets mode: +v achuith
[20:04:32] *** saintlou has quit IRC
[20:05:02] *** rbyers_ has quit IRC
[20:05:07] <grundler>   JSONInterfaceError: Automation call {'username': 'performancetestaccount at gmail dot com', 'password': 'perfsmurf', 'command': 'Login'} received empty response.  Perhaps the browser crashed.
[20:05:07] <grundler> BVT failure is result of Chrome failure? http://cautotest/results/66211-chromeos-test/group0/172.31.26.66/login_CryptohomeUnmounted/status
[20:08:01] <kliegs> grundler: sorry - still have meetings. but should have a buildspec being rev'd through
[20:08:05] <kliegs> i'll be back shortly
[20:09:03] *** saintlou has joined #chromium-os
[20:09:04] *** ChanServ sets mode: +v saintlou
[20:09:22] <grundler> kliegs: np - checking BVT failures now
[20:16:15] <dalecurtis> grundler: I think that's correct, or at least that's the same conclusion I came to.
[20:16:48] <grundler> yeah...looks like 20323 again.
[20:17:03] <grundler> I didn't realize there was a much longer thread already on that particular failure.
[20:23:27] *** radhermit has quit IRC
[20:24:05] *** radhermit has joined #chromium-os
[20:24:52] <ellyjones> is the current orthodoxy to have packages install their own init scripts, or to keep them all in platform/init?
[20:25:58] <ellyjones> I assume it's to install their own init scripts, which I call the 'making sense' approach
[20:26:26] <cmasone> ellyjones: ping jrbarnette on chat
[20:26:31] *** chocobo__ has joined #chromium-os
[20:26:31] <grundler> I don't know the preferred convention...jrbarnette would be the person I'd ask.
[20:26:31] *** ChanServ sets mode: +v chocobo__
[20:27:22] <gauravsh> the latter makes more sense to me. since startup order and dependencies matter. but yeah, what cmasone and grundler said.
[20:27:59] <ellyjones> startup order and dependencies are expressed by 'depends on' in the upstart job though
[20:28:11] <ellyjones> ok, jrbarnette says with the package
[20:28:28] <nirnimesh> kliegs: So did Zel's fix for 20323 not work?
[20:29:10] <cmasone> nirnimesh: read backscroll
[20:29:26] <grundler> achuith, ok if I take off for lunch? looks like trees are turning green again
[20:30:23] <grundler> I can dig into tangent-binary builder if waterloo folks aren't aware of those failure yet.
[20:30:56] * grundler heads off for early lunch...bb in 45 min about
[20:31:22] <achuith> grundler: sure, I'll be around
[20:31:50] <grundler> 'k thanks :)
[20:33:20] <dgarrett> I have a request for today's sheriffs....
[20:34:03] <dgarrett> Trying to work on but 19198 (flaky KVM hangs), and would like to know if you can capture something for me if the problem presents again today or tomorrow.
[20:36:39] <dgarrett> Basically, just try to ssh into the KVM.
[20:36:46] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_asymptote canary" from None: )'
[20:37:03] <dgarrett> The bug has instructions. http://code.google.com/p/chromium-os/issues/detail?id=19198
[20:37:16] *** BladeFreak has joined #chromium-os
[20:39:29] <cwolfe> kliegs says: known issue, tell grundler to re-open
[20:39:34] *** BladeFreak has quit IRC
[20:40:01] <cwolfe> (in reference to the asymptote canary closing. Context good)
[20:40:41] *** BladeFreak has joined #chromium-os
[20:42:41] <cwolfe> achuith: ^
[20:42:57] <achuith> hi
[20:42:58] <cwolfe> that's what I get for not reading the channel
[20:43:01] *** BladeFreak has quit IRC
[20:44:11] <crosbot> tree became 'Tree is closed (achuith investigating tegra2_asymptote canary failure http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[20:44:56] <achuith> cwolfe: what you just said
[20:44:58] <crosbot> tree became 'Tree is open (http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[20:45:26] *** arun_ has joined #chromium-os
[20:49:10] *** chocobo__ has quit IRC
[20:49:48] <jennyz> i build the chrome with chromeos=0 and toolkit_views=1, the chrome UI was weird, the refresh button shows a "X" as close, but it reloads actually, the new tab button does not work either, I tried a clean build, and start chrome with a clean profile directory, no help, anyone has clue?
[20:52:43] <kliegs> nirnimesh: zel's fix didn't make it into the build. eblake has cut a new release branch which should get it in
[20:54:52] <kliegs> jennyz: you might be better suited in #chromium for that if you're not building for chromeos.  But I believe that configuration isn't overly tested
[20:55:49] *** zizanie has joined #chromium-os
[20:56:21] <jennyz> kliegs: I will post it on #chromium, thx!
[20:57:42] <zizanie> Hello, anyone knows if irssi can be ported to chromium os ?
[20:58:03] <zizanie> or if this has been done already
[20:58:22] <ellyjones> 'ported to'?
[20:58:30] <ellyjones> if you have a developer build, you can just gmerge it onto the target
[20:58:45] <ellyjones> if you don't, you can't install additional native software anyway
[20:59:59] <zizanie> ellyjones: right now I'm on hexxeh's vanilla build, I think it is a develloper build
[21:00:15] <ellyjones> ask hexxeh, then
[21:00:32] <ellyjones> chromium os is just linux under the covers, but how you install packages may vary
[21:01:05] *** BladeFreak has joined #chromium-os
[21:02:04] <zizanie> ellyjones: I'm looking to buy a chromebook, I know that I can't install native software on it but maybe irssi on an USB key can be run this way on a chromebook ?
[21:03:44] <ellyjones> no, you cannot run native code in non-developer mode
[21:03:49] <ellyjones> that is intentional and part of the security model
[21:04:09] <ellyjones> if you put it into developer mode you can install a developer build or get a shell and do whatever you like, though
[21:06:17] <zizanie> ellyjones: ok, very interesting, I think the only restriction on a chromebook is that I can't run a live USB distribution 'cause the bios is locked, is this right ?
[21:07:11] <ellyjones> there is no bios per se
[21:07:17] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "lumpy-binary" from 20edc1e16f8917772380f651370fa4e0f740bf99: jam at chromium dot org <jam at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[21:07:27] <ellyjones> in brief: there are two modes, normal mode and developer mode; moving between them is controlled by a physical switch
[21:07:40] <ellyjones> in normal mode, the chromebook will only boot system images signed by Google
[21:07:56] <ellyjones> and there is no facility for getting a shell or similar, nor any way to mount external media as executable
[21:08:06] <ellyjones> in developer mode, the chromebook will boot any code off a USB stick or the SSD
[21:08:25] <ellyjones> and will expose a shell when booted off the SSD (if you left Chrome OS installed), which you can use to run arbitrary binaries
[21:08:29] <ellyjones> make sense?
[21:09:20] <crosbot> tree became 'Tree is open (http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "lumpy-bin" failed with 20323 again)'
[21:09:27] <kliegs> :(  new build spec not there yet
[21:09:41] <zizanie> ellyjones: yes, thanks a lot for your lights
[21:20:50] <grundler> wow...tree is green :)
[21:21:01] <grundler> oh...not internal tree :(
[21:21:24] *** randomubuntuguy has quit IRC
[21:29:01] *** petermayo has quit IRC
[21:41:57] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_arthur-binary" from ffe0718e93e6cb4cf72d4f159710b45d79521e00: Ryan Cui <rcui at google dot com>)'
[21:42:59] <crosbot> tree became 'Tree is closed (achuith investigating tegra2_arthur-binary http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[21:43:24] <grundler> heh..achuith is a bit faster than me :)
[21:43:41] <achuith> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/tegra2_arthur-binary/builds/1541/steps/Archive/logs/stdio
[21:44:35] <achuith> buildspec?
[21:44:41] <grundler> Failed chromeos-base/chromeos-initramfs-0.0.1-r46 (in 0m2.0s). Your build has failed.
[21:45:36] <grundler> chromeos-initramfs-0.0.1-r46: cp: cannot stat `/build/tegra2_arthur//usr/lib/libpng12.so.0.44.0': No such file or directory
[21:46:01] <grundler> WTF...I thought rev'd libs was two days ago...no?
[21:47:14] <achuith> It built successfully less than 2 hours ago...
[21:48:02] <grundler> so did libpng12 get rev'd ?
[21:48:07] <grundler> (since then)
[21:48:13] <grundler> not sure how to check that offhand...
[21:48:24] <grundler> I guess look through commits.
[21:48:36] <achuith> I wish there was an easy way to search commits
[21:49:13] <grundler> uhoh. Most of the builds just failed.
[21:49:58] <achuith> that's a lot of redness
[21:50:40] <grundler> achuith: mousing over the commits listed on the waterfall page shows log comment
[21:51:04] <achuith> ok, libpng failure is real
[21:51:13] <kliegs> always nice to see a real failure and not flake
[21:51:23] <kliegs> the waterfall commit log isn't always accurate
[21:51:23] *** zizanie has quit IRC
[21:56:38] <achuith> looks like libpng got revved?'
[21:57:35] <kliegs> looks like it - http://gerrit.chromium.org/gerrit/7880
[21:57:48] <kliegs> just got in ~90 minutes ago
[21:59:38] <achuith> yup, that's our man
[22:00:08] <grundler> let me see if david james is at his desk...he might know what's wrong here.
[22:00:10] <kliegs> is mtennant around? don't see on irc
[22:00:16] <kliegs> zbehan: ping
[22:00:26] <kliegs> i recall zbehan fixing a bug like this elsewhere once
[22:00:26] <achuith> I pinged mtennant on chat
[22:01:48] <achuith> mtennant taking a look
[22:01:52] <kliegs> achuith: i wonder if just rev'ing chromeos-initramfs will fix it
[22:02:27] <grundler> I just talked with mtennant (he was at his desk, david james wasn't but both share an office)
[22:02:29] <achuith> kliegs: it seems like that's what's needed
[22:02:39] <kliegs> submit a noop change for it then?
[22:04:05] <kliegs> sound good?
[22:04:28] <achuith> kliegs: sgtm
[22:04:53] <kliegs> http://gerrit.chromium.org/gerrit/8153
[22:05:07] * grundler has no clue why rev'ing initramfs is needed...shouldn't it automatically pick up the latest libpng if it's a dep?
[22:05:37] *** mtennant has joined #chromium-os
[22:05:37] *** ChanServ sets mode: +v mtennant
[22:06:30] <kliegs> grundler: file a bug on that I guess.  I think (by design?) the binary bots only rev packages that change and don't redo the dependency tree
[22:06:34] <kliegs> at least that's what the log looks like
[22:07:23] <achuith> kliegs: thanks!
[22:07:49] <mtennant> Can I help?
[22:07:51] <kliegs> i'm inclined to let current run finish on the bots.  as they seem mostly done and I always seem to hit 'stop build' at the point where it breaks things
[22:08:15] <kliegs> leave closed until we see one go green?
[22:08:57] <grundler> mtennant: I suspect it
[22:09:03] <grundler> 's not a problem with your change directly
[22:09:09] <achuith> kliegs: ok, sgtm
[22:09:26] <kliegs> mtennant: what grundler said - looks like your change triggered an issue elsewhere
[22:09:48] <mtennant> ok.  I don't have the chat context above.
[22:10:11] <grundler> kliegs: I don't think you CL will fix...talking with msb. He says the revision is hard coded in the ebuild for initramfs
[22:10:12] <kliegs> mtennant: chromeos-initramfs was trying to run the acrhive_build step using the .44 version of libpng.  which didn't exist since your change rev'd it to .45
[22:10:29] <grundler> we need to rewrite the ebuild
[22:10:40] <mtennant> Is it simply a failure in the build-after-sync scenario, then?
[22:10:44] <kliegs> oh. crap
[22:10:46] <kliegs> i'll just go update that
[22:10:58] <grundler> no...ebuild is hardcoded with a revision instead of generating one
[22:11:03] <mtennant> ah
[22:11:09] <grundler> (in initramfs)
[22:11:49] <grundler> kliegs: ok - we can rev that for now but open a P0 bug to rewrite the ebuild correctly.
[22:11:55] <grundler> I'll open the P0 bug now.
[22:12:10] <kliegs> ok.
[22:12:22] <msb_> http://git.chromium.org/gitweb/?p=chromiumos/overlays/chromiumos-overlay.git;a=blob;f=chromeos-base/chromeos-initramfs/chromeos-initramfs-9999.ebuild
[22:12:50] <msb_> a whole bunch of hard-coding of library version
[22:12:51] <kliegs> http://gerrit.chromium.org/gerrit/8155
[22:12:56] <kliegs> msb_: yah. ugly
[22:13:28] <grundler> msb is wandering over to jrbarnette's desk to explain the problem
[22:13:38] <kliegs> grundler: is it ok to submit the update to hardcoding?
[22:13:42] <kliegs> grundler: or is a better fix coming?
[22:13:45] <crosbot> tree became 'Tree is closed (kliegs->http://gerrit.chromium.org/gerrit/#change,8153 waiting for one builder to cycle green http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[22:13:54] <grundler> kliegs: please submit the hardcoding
[22:14:12] <kliegs> in
[22:14:13] <msb_> kliegs: I'd update the hard-coding and leave the bug open for someone to fix
[22:14:23] <msb_> properly
[22:14:46] <kliegs> msb_: done
[22:14:58] <kliegs> x86 generic pfq about to fail with same problem.
[22:15:33] <achuith> The ebuild change
[22:15:36] <mtennant> looks like you guys got it under control.  I'm heading to lunch then
[22:15:58] <mtennant> Sorry I didn't catch this, but I can't seem to find which board builds this package right now.
[22:16:14] <achuith> nm
[22:16:50] <crosbot> tree became 'Tree is closed (kliegs->http://gerrit.chromium.org/gerrit/#change,8155 waiting for one builder to cycle green http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[22:19:03] <msb_> kliegs: did you open a bug?
[22:19:13] <kliegs> msb_: no - grundler said he was opening one
[22:19:22] <msb_> ah
[22:22:46] <grundler> http://code.google.com/p/chromium-os/issues/detail?id=20730
[22:22:52] <kliegs> hmm. the new chrome build release doesn't seem to have rev'd yet
[22:23:49] <grundler> mtennant: thanks - internal builds for most machines failed
[22:23:53] <kliegs> x86 generic pfq running again with new change. so lets see.
[22:24:54] * grundler had trouble submitting the bug...text editor didn't like me pasting in URLs >:(
[22:26:35] <kliegs> nevermind - I see it now
[22:26:49] <kliegs> the next build should have zel's fix for the offline bug
[22:26:55] <kliegs> and should also clear asymptote and tangent errors
[22:30:59] *** rharrison_chrome has quit IRC
[22:34:49] *** rbyers_ has joined #chromium-os
[22:35:36] <achuith> ya, I heard zel's change landed
[22:36:01] <achuith> for the portal mode webui fix
[22:36:42] <kliegs> achuith: I don't believe we've had any builds yet using it, but all future ones should now
[22:37:26] <achuith> awesome, I think we hit that failure 2-3 times yesterday
[22:38:00] <kliegs> achuith: if only that you were lucky.  seen it a lot today
[22:38:50] *** wfrichar has quit IRC
[22:39:38] <grundler> is that for 20323?
[22:39:39] <achuith> Away 15 min
[22:39:39] <grundler> (we hit that at least 8 times)
[22:39:55] <achuith> yup
[22:39:58] <achuith> 20323
[22:40:08] <achuith> I didn't realize it was that many
[22:40:53] <grundler> "palest ink is stronger than the best memory." -- chinese proverb (and I'm probably recalling it wrong)
[22:41:05] <kliegs> grundler: should've written it down :)
[22:41:12] <grundler> :)
[22:41:19] <grundler> probably have...just need to find it. :)
[22:41:20] <achuith> grundler is keeping track :)
[22:41:49] <kliegs> he's got a list
[22:42:54] <grundler> I've summarized observations for yesterday in the sites page: chrome > Resources? > ?Tree closure postmortems? > ?20110921
[22:43:34] <grundler> "The palest ink lasts longer than the most retentive memory." looks like a literal translation but sounds right
[22:45:17] <grundler> Hrm..another variant that sounds good: "the faintest ink is more powerful than the strongest memory"
[22:45:59] <davidjames> the pen is mightier than the brain
[22:46:54] * grundler imagines a pretty violent version of paper, rock, scissors with the brain losing to a pen :)
[22:48:36] <rcui> grundler: sounds like something from a fortune cookie ;)
[22:49:19] <rcui> oh woops, just read that it actually is a chinese proverb
[22:50:21] <grundler> :)
[23:00:59] *** Styx has quit IRC
[23:02:13] <grundler> kliegs: just to double check, we should see the "webkit patch" build failure in tegra2_seaboard-tangent-binary builds to go away shortly?
[23:02:54] *** Styx has joined #chromium-os
[23:03:57] <kliegs> grundler: correct.  its a side effect of chrome being rev'd (the change comes from the -9999 build which is the base for whenever a new release branch is made)
[23:04:11] <grundler> kliegs: ok - thanks :)
[23:05:06] <kliegs> i'm showing green on the pfq's and guessing the internal binaries should be green soon
[23:05:08] <kliegs> reopen?
[23:05:45] *** TW1920 has quit IRC
[23:05:52] <kliegs> stumpy, lumpy, zgb & alex might take one more cycle looking at the timings on the tree
[23:06:20] <grundler> I'm willing to wait if it's less than another hour.
[23:06:44] <grundler> any ETA < hour, I  meant
[23:10:24] <grundler> kliegs: while that works out nicely for my TZ, hows that look in EST? getting late in the day I think, right?
[23:11:27] <kliegs> 5 pmish. so leaving in ~1 hour
[23:11:34] <achuith> back
[23:11:44] <kliegs> so might be around when I'm leaving
[23:15:53] <grundler> hrm. zgb failed as expected.
[23:16:20] <grundler> Packages failed: chromeos-base/chromeos-initramfs-0.0.1-r46
[23:16:29] <grundler> can ignore that.
[23:16:30] <kliegs> yup.  next run should be green for it
[23:17:15] <kliegs> x86 generic  pfq went green after being red from this.  as well as internal x86 pfq.  so suspect this will be fine
[23:17:58] <kliegs> everything but stumpy & lumpy should go green next cycle
[23:18:14] <kliegs> i'm going to just kill stumpy & lumpy now - they've still got 40+ minutes to go
[23:18:27] <grundler> ok - that sounds reasonable'
[23:18:49] <grundler> and I think you are right. At least odds are good.
[23:19:08] *** jochen__ has quit IRC
[23:19:09] *** Honoome has quit IRC
[23:19:09] *** SeligArkin has quit IRC
[23:19:09] *** jennb has quit IRC
[23:19:58] <kliegs> alex just failed as well so it should cycle as well
[23:20:20] <kliegs> given any changes made now will wait until the next cycles its probably fine to open.  we should have a red=>green=>red transition if something else bad gets in
[23:21:59] *** Styx has quit IRC
[23:22:12] *** saintlou has quit IRC
[23:22:56] *** jochen__ has joined #chromium-os
[23:22:56] *** Honoome has joined #chromium-os
[23:22:56] *** SeligArkin has joined #chromium-os
[23:22:56] *** jennb has joined #chromium-os
[23:22:56] *** holmes.freenode.net sets mode: +vv jochen__ jennb
[23:23:41] *** saintlou has joined #chromium-os
[23:23:41] *** ChanServ sets mode: +v saintlou
[23:27:25] *** saintlou has quit IRC
[23:32:36] *** saintlou has joined #chromium-os
[23:32:36] *** ChanServ sets mode: +v saintlou
[23:37:49] <achuith> kliegs, grundler: should I just reopen then?
[23:38:07] <achuith> we've been closed a while on this
[23:38:18] <grundler> yeah, I think I'm ok with re-opening.
[23:38:35] <achuith> Should I throttle?
[23:38:38] <achuith> or just open?
[23:38:43] <grundler> right, but it's closed because we'd like to confirm fixes in place really work.
[23:39:19] <achuith> ok, we should probably wait for a builder to cycle green
[23:39:39] <achuith> none have so far
[23:40:19] <grundler> and I'm pretty sure the ETA is fictional :(
[23:41:05] <grundler> achuith: VMtest seems to have passed - so at least one issue didn't trigger :)
[23:42:48] <achuith> ok, hopefully we're not too far
[23:47:51] *** Kyngdom has joined #chromium-os
[23:50:09] <crosbot> tree became '?'
[23:50:25] <crosbot> tree became 'Tree is closed (kliegs->http://gerrit.chromium.org/gerrit/#change,8155 waiting for one builder to cycle green http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[23:52:36] <achuith> tegra2_kaen-binary succeeded
[23:52:54] <achuith> I'm going to open the tree and throttle until the rest of the builders go green
[23:52:55] *** rbyers_ has quit IRC
[23:53:00] <grundler> +1
[23:53:30] <crosbot> tree became 'Tree is throttled (waiting for builders to cycle green http://codereview.chromium.org/7994006/ --> new chromium buildspec for ChromiumOS; "x86 generic PFQ" failed with 20323 again)'
[23:55:29] *** rbyers_ has joined #chromium-os
[23:55:30] *** ChanServ sets mode: +v rbyers_
[23:59:45] *** rbyers_ has quit IRC





top