[00:04:02] <DeezeNuts> is it possible to upgrade the SSD in the cr48?
[00:05:10] *** achuith_ has joined #chromium-os
[00:05:16] *** ChanServ sets mode: +v achuith_
[00:06:10] *** achuith has quit IRC
[00:06:10] *** achuith_ is now known as achuith
[00:11:58] <wfrichar> DeezeNuts: I've seen people claim that they've done it without problems, in some of the public chrome enthusiastic forums. I've never tried it myself.
[00:11:59] *** kerz has quit IRC
[00:20:26] *** fluffman has joined #chromium-os
[00:22:33] * fluffman needs a wl driver integrated into official builds.
[00:22:41] <fluffman> that is all.
[00:23:54] <vpalatin> fluffman: send a patch for the kernel configuration and add me as reviewer (vpalatin)
[00:29:08] <wfrichar> I'm still looking at the tree failure. Has anyone changed the kernel command line args recently?
[00:29:18] <wfrichar> I can't figure out how the AU test ever worked.
[00:29:37] <wfrichar> Because chromeos-setgoodkernel is failing to identify the running image.
[00:33:21] *** saintlou has quit IRC
[00:37:36] <DeezeNuts> wfrichar, i just want more space for ubuntu
[00:37:47] *** behdad has quit IRC
[00:37:54] <DeezeNuts> is it possible to delete chrome os and just keep ubuntu
[00:39:13] <wfrichar> DeezeNuts: Sure.
[00:39:32] <DeezeNuts> how would i go about doing that
[00:39:36] <DeezeNuts> without messing up ubuntu
[00:39:59] <wfrichar> Are you on a Cr-48 or something else?
[00:41:34] *** sadrul has quit IRC
[00:49:15] <gauravsh> what's the deal with the tree?
[00:51:34] <wfrichar> gauravsh: it's busted. I've been looking at it for a couple of hours and can't figure out why.
[00:51:42] <wfrichar> Come on over and join the party if you want.
[00:53:08] <gauravsh> I didn't know if it was being looked at. That's why I asked. Maybe the tree status should be updated to reflect that?
[00:56:22] <ellyjones> the x86-mario-binary buildbot failed because its kvm instance hung
[00:56:29] <ellyjones> I went off to look for the bug for this and got distracted
[00:56:52] <crosbot> tree became 'Tree is closed (it's busted real good - and yes, I'm looking at it).'
[00:57:31] <gauravsh> haha, perfect
[01:00:19] *** achuith has quit IRC
[01:01:53] *** achuith has joined #chromium-os
[01:01:54] *** ChanServ sets mode: +v achuith
[01:06:01] <gauravsh> git config --global review.gerrit.chromium.org/gerrit.autoupload true
[01:06:23] <gauravsh> solves one of the most annoying things I find about repo upload
[01:06:28] <cmasone> gauravsh: wow.  Poignant.
[01:06:42] *** DeezeNuts has quit IRC
[01:06:51] <micahc> gauravsh: what is the annoying thing it solves?
[01:07:42] <gauravsh> have you ever done a repo upload ., switched the window, wonder why the reviewer didn't lgtm it after an hour
[01:07:47] <gauravsh> only to glance at the original window and see:
[01:07:54] <gauravsh> Upload project ... to
[01:08:03] <gauravsh> to gerrit.chromium.org/gerrit (y/n)?
[01:08:44] <wfrichar> OKay. I've got a kvm instance running the AU test, and when it tries to reboot.... nothing happens.
[01:08:59] <wfrichar> Lots of processes die, but it doesn't actually reboot.
[01:09:20] <micahc> gauravash: I have done that.  Thanks for the fix :)
[01:15:26] <arkaitzr> repo branches
[01:15:32] *** dtu has quit IRC
[01:15:34] <arkaitzr> upps wrong window
[01:16:40] <davidjames> wfrichar: So the only difference between the bots that are failing and the bots that are succeeding is jglasgow's change to init.git, right?
[01:16:50] <wfrichar> maybe.
[01:16:55] <wfrichar> possibly.
[01:17:09] <wfrichar> sosa says "and maybe prebuilts"
[01:18:19] <davidjames> wfrichar: All builders that don't uprev external pkgs are working, right? Can't find any other failures
[01:19:22] <wfrichar> O
[01:19:25] <wfrichar> j
[01:19:31] <wfrichar> stupid keyboard.
[01:19:44] <wfrichar> I'm gonna try a manual revert of that one change and see if it makes a difference.
[01:20:01] <davidjames> wfrichar: Yeah might as well, since it's the only obvious difference between working and non-working
[01:21:23] *** Keybuk has quit IRC
[01:24:21] *** marklarson has joined #chromium-os
[01:33:58] *** sergiu has joined #chromium-os
[01:33:58] *** sergiu has joined #chromium-os
[01:41:09] <wfrichar> Update: http://gerrit.chromium.org/gerrit/#change,4686
[01:41:39] <wfrichar> I've reverted the cromo change from this morning. With that change, the kvm instance refuses to reboot. Without it, it reboots just fine. No clue why.
[01:42:04] <wfrichar> I IM'd the author, but he's AFK.
[01:43:07] <wfrichar> I have to run to a meeting. back in while.
[01:46:26] <vlaviano> rochberg is in town and familiar with cromo, so I asked him to take a look
[01:48:00] *** achuith_ has joined #chromium-os
[01:48:00] *** ChanServ sets mode: +v achuith_
[01:52:28] *** achuith has quit IRC
[01:52:28] *** achuith_ is now known as achuith
[01:52:55] *** BladeFreak has quit IRC
[01:53:45] <crosbot> tree became 'Tree is open (fixes/reversions applied, expect builds to cycle green)'
[01:56:40] *** lipsinV2 has joined #chromium-os
[02:01:43] *** kerz has joined #chromium-os
[02:01:43] *** ChanServ sets mode: +v kerz
[02:03:42] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_arthur-binary" from b3c9dd097b9db87290001715c0add9ebbc309b5f: creis at chromium dot org <creis at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>, rginda at chromium dot org <rginda at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>, rogerta at chromium dot org <rogerta at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[02:05:04] <wfrichar> Now what.
[02:07:53] <vlaviano> looks like that build includes sjg's fix, but issue seems to be something different: missing dependencies
[02:11:31] *** rbyers has joined #chromium-os
[02:13:39] *** rbyers has quit IRC
[02:14:12] *** rbyers has joined #chromium-os
[02:14:13] *** ChanServ sets mode: +v rbyers
[02:14:24] <crosbot> tree became 'Tree is closed (investigating internal build failure)'
[02:14:45] *** behdad has joined #chromium-os
[02:15:44] *** achuith has quit IRC
[02:15:51] *** achuith has joined #chromium-os
[02:15:51] *** ChanServ sets mode: +v achuith
[02:17:36] *** BladeFreak has joined #chromium-os
[02:21:14] *** sadrul has joined #chromium-os
[02:21:14] *** ChanServ sets mode: +v sadrul
[02:21:40] <vlaviano> marcheu working on a fix for build failure, should have the tree open again soon
[02:24:30] <cmasone> vlaviano: x86-generic pfq failed tests again
[02:24:31] *** rbyers has quit IRC
[02:24:48] <vlaviano> ugh
[02:33:41] <sosa> davidjames: i'm wondering whether the fd stuff you did has broken the test harness?
[02:37:12] *** saintlou has joined #chromium-os
[02:37:12] *** ChanServ sets mode: +v saintlou
[02:39:07] <davidjames> sosa: Hm, why? pineview binary passed fine
[02:39:29] <davidjames> sosa: Also internal pfq passed successfully several times
[03:01:10] *** Styx has quit IRC
[03:03:28] <zbehan> vlaviano, wfrichar: will it be ok if i push a change that does not affect any live code? http://gerrit.chromium.org/gerrit/4500
[03:10:37] *** saintlou has quit IRC
[03:11:25] *** rbyers has joined #chromium-os
[03:11:25] *** ChanServ sets mode: +v rbyers
[03:18:23] *** rbyers_ has joined #chromium-os
[03:19:40] *** jglasgow_ has joined #chromium-os
[03:19:51] *** jglasgow_ has quit IRC
[03:19:58] *** jglasgow_ has joined #chromium-os
[03:19:58] *** ChanServ sets mode: +v jglasgow_
[03:19:59] *** rbyers_ has quit IRC
[03:22:08] *** rbyers has quit IRC
[03:22:53] *** rhelmer has joined #chromium-os
[03:23:15] <vlaviano> zbehan: go ahead
[03:31:58] *** sergiu has quit IRC
[03:39:19] *** wfrichar has quit IRC
[03:40:17] *** deshantm_away is now known as deshantm
[03:47:01] <crosbot> tree became 'Tree is open (filed issue 18191 for transient kvm error)'
[03:47:43] *** kmixter has quit IRC
[03:52:19] *** jglasgow_ has quit IRC
[03:52:48] *** jrbarnette has quit IRC
[03:57:20] *** vlaviano has quit IRC
[04:29:20] *** mascond0 has quit IRC
[04:30:14] *** mascondante has joined #chromium-os
[04:32:55] *** behdad has quit IRC
[04:45:31] *** BladeFreak has quit IRC
[04:51:45] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot_master" on "x86 generic pre flight queue" from aa4761cc3647f2bf2e88f5de8e4d740973a1d0e8: Simon Que <sque at chromium dot org>, ihf at chromium dot org <ihf at chromium dot org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c>)'
[04:59:07] <ihf> This failure was seen already this morning, see
[04:59:08] <ihf> http://build.chromium.org/p/chromiumos/builders/x86%20generic%20pre%20flight%20queue/builds/6571/steps/Report/logs/stdio
[04:59:19] <ihf> It has nothing to do with the current commits.
[05:06:25] *** oc80z has quit IRC
[05:07:12] *** oc80z has joined #chromium-os
[05:09:20] *** Inumedia has quit IRC
[05:11:01] <sosa> davidJames: sorry i was getting confused with all the tput errors
[05:11:16] <sosa> which may be fall out from your changes to clean up the fd's
[05:23:22] <crosbot> tree became 'Tree is open (ihf: hitting flaky x86 generic pre flight queue that has been around for a while)'
[05:38:39] <crosbot> tree became 'Tree is closed (a dozen tests segfault in chrome across multiple builders; something is actually wrong)'
[05:42:04] *** lipsinV2 has quit IRC
[05:42:34] *** lipsinV2 has joined #chromium-os
[05:59:03] *** lipsinV2 has quit IRC
[05:59:32] *** lipsinV2 has joined #chromium-os
[06:01:37] *** petermayo has quit IRC
[06:24:47] *** Justasic has quit IRC
[06:30:13] *** Justasic has joined #chromium-os
[06:31:20] *** Adys has quit IRC
[06:38:08] *** D|sT has joined #chromium-os
[06:38:41] *** Adys has joined #chromium-os
[06:48:00] <yusukes> sheriffs: can i submit a tiny autotest change? http://gerrit.chromium.org/gerrit/#change,4720
[06:48:16] <yusukes> the CL has to be in R14 to keep autotest bots for R14 green..
[07:07:50] *** Inumedia has joined #chromium-os
[07:09:07] *** rsleevi has quit IRC
[07:09:15] *** rsleevi has joined #chromium-os
[07:10:10] *** tbarzic_ has joined #chromium-os
[07:22:03] *** vmil86 has joined #chromium-os
[07:24:02] *** Adys has quit IRC
[07:43:17] *** Adys has joined #chromium-os
[07:59:53] *** achuith has quit IRC
[08:04:07] <crosbot> tree became 'Tree is closed (a dozen tests segfault in chrome across multiple builders; maybe crosbug.com/17899 got worse?)'
[08:31:39] *** Styx has joined #chromium-os
[08:31:56] *** Adys has quit IRC
[08:32:00] *** Styx has quit IRC
[08:32:04] *** Styx__ has joined #chromium-os
[08:35:54] *** Styx has joined #chromium-os
[08:36:35] *** Adys has joined #chromium-os
[08:40:05] *** Adys has quit IRC
[08:44:34] *** Adys has joined #chromium-os
[08:44:49] *** achuith has joined #chromium-os
[08:46:48] *** achuith has quit IRC
[09:00:07] *** Styx has quit IRC
[09:00:16] *** Styx__ is now known as Styx
[09:02:39] *** Adys has quit IRC
[09:10:43] *** Adys has joined #chromium-os
[09:13:40] *** achuith has joined #chromium-os
[09:17:05] *** ScriptRipper has quit IRC
[09:17:21] *** ScriptRipper has joined #chromium-os
[09:17:45] *** ScriptRipper has joined #chromium-os
[09:26:38] *** tbarzic_ has quit IRC
[09:27:59] *** Adys has quit IRC
[09:46:08] *** Adys has joined #chromium-os
[09:50:08] *** mascondante has quit IRC
[09:58:25] *** arun has quit IRC
[10:12:01] <steev_> is chromium (the browser) being tested on 32bit anymore?
[10:14:10] *** achuith has joined #chromium-os
[10:26:29] <crosbot> tree became 'Tree is closed (xwininfo fix is on the way; a dozen tests segfault in chrome across multiple builders; maybe crosbug.com/17899 got worse?)'
[10:29:18] *** jochen__ has quit IRC
[10:29:24] *** jochen__ has joined #chromium-os
[10:29:25] *** ChanServ sets mode: +v jochen__
[10:44:18] *** arun has joined #chromium-os
[10:44:19] *** arun has joined #chromium-os
[10:56:07] *** achuith has quit IRC
[11:02:56] *** kannan has joined #chromium-os
[11:36:45] *** patcito has quit IRC
[12:01:11] *** cjb has quit IRC
[12:02:52] *** cjb has joined #chromium-os
[12:36:16] *** quannnum_ has quit IRC
[12:37:22] *** quannnum has joined #chromium-os
[12:39:04] *** kannan has quit IRC
[14:52:42] *** nick761_ has joined #chromium-os
[14:54:21] *** nick761 has quit IRC
[14:57:10] *** nick761_ has quit IRC
[14:57:23] *** petermayo has joined #chromium-os
[14:57:41] *** nick761 has joined #chromium-os
[15:11:47] *** sadrul has quit IRC
[15:23:04] *** rbyers has joined #chromium-os
[15:30:06] *** ScriptRipper has quit IRC
[15:33:48] *** SoulRaven has joined #chromium-os
[15:37:46] *** ScriptRipper has joined #chromium-os
[15:37:52] *** ScriptRipper has joined #chromium-os
[15:47:25] *** rharrison_chrome has joined #chromium-os
[15:47:25] *** ChanServ sets mode: +v rharrison_chrome
[15:54:20] *** sadrul has joined #chromium-os
[15:54:20] *** ChanServ sets mode: +v sadrul
[15:55:32] *** petermayo has quit IRC
[16:10:43] *** nick761 has quit IRC
[16:11:44] *** nick761 has joined #chromium-os
[16:19:22] *** kgunnit has joined #chromium-os
[16:34:49] *** petermayo has joined #chromium-os
[16:35:15] *** petermayo_ has joined #chromium-os
[16:35:16] *** ChanServ sets mode: +v petermayo_
[16:39:19] *** petermayo has quit IRC
[16:39:19] *** petermayo_ is now known as petermayo
[16:48:10] <ellyjones> does build_image actually build a kernel? oO
[16:51:55] *** Blinny has joined #chromium-os
[16:53:19] *** benchan_ has quit IRC
[16:53:26] *** benchan has joined #chromium-os
[16:53:26] *** ChanServ sets mode: +v benchan
[16:54:34] *** jrbarnette has joined #chromium-os
[17:00:51] <petermayo> How are the sheriffs doing today?
[17:01:00] *** tfarina has joined #chromium-os
[17:01:15] *** tfarina has left #chromium-os
[17:01:20] <ellyjones> oh
[17:01:25] <ellyjones> asleep at the wheel, evidently :)
[17:01:50] * ellyjones will start looking
[17:02:27] <ellyjones> the pfq: chrome is segfaulting during all the tests
[17:02:36] <ellyjones> well, not _all_, but a lot
[17:03:26] <ellyjones> x86-generic-full failed because of a missing xcb
[17:04:11] <petermayo> I thought the xwininfo fix fixed that, but I see it hasn't started again.
[17:04:16] <petermayo> I'll poke it.
[17:05:26] <ellyjones> alright
[17:08:57] <petermayo> interesting ... a lot of fulls looked like they were in a funny queue state.
[17:09:56] *** jrbarnette_ has joined #chromium-os
[17:09:59] <petermayo> maybe just stuck behind the PFQ failures.
[17:10:27] *** D|sT has quit IRC
[17:11:34] *** lipsinV2 has quit IRC
[17:11:46] *** lipsinV2 has joined #chromium-os
[17:12:42] <ellyjones> hrm
[17:12:55] <ellyjones> so our main problem is that chrome is segfaulting a lot on the pfq
[17:12:59] *** jrbarnette has quit IRC
[17:12:59] *** jrbarnette_ is now known as jrbarnette
[17:14:11] <cmasone> ellyjones: yup.  At least it's happening all the time now, instead of once in a blue moon
[17:14:31] <cmasone> ellyjones: can we determine when that changeover happened?
[17:14:35] <cmasone> ellyjones: it happens on logout
[17:14:43] <cmasone> ellyjones: so, any test that logs out seems to trigger it now
[17:15:59] <ellyjones> build 6857 is where it started
[17:17:13] <petermayo> 6587 you mean?
[17:17:29] <cmasone> that makes simon's changes suspicious
[17:18:07] <ellyjones> yeah, 6587
[17:18:10] <ellyjones> yes
[17:18:44] * ellyjones goes to take a look at it
[17:19:25] <ellyjones> I don't know anything about chrome, though
[17:19:48] <cmasone> ellyjones: simon's changes aren't in chrome :-)
[17:20:25] <cmasone> ellyjones: also, davemoore has expressed a willingness to investigate issues like this if we say "it wasn't happening in chrome version X, and started happening in chrome Y"
[17:20:51] <ellyjones> well, the only change in chrome revision was aa4761cc3647f2bf2e88f5de8e4d740973a1d0e8
[17:21:00] <ellyjones> which seems implausible, since we're on x86
[17:22:35] <cmasone> ellyjones: oh, we don't follow Tot Chrome
[17:22:48] <cmasone> ellyjones: so you'd have to check what chrome ebuld was marked stable at that point
[17:23:12] <ellyjones> how do I go about that?
[17:23:27] <cmasone> I usually use gitweb to check
[17:24:38] <ellyjones> oh, that just means chromium/src.git?
[17:25:01] <cmasone> chromiumos/overlays/chromiumos-overlay.git
[17:27:25] <crosbot> tree became 'Tree is closed (a dozen tests segfault in chrome across multiple builders; maybe crosbug.com/17899 got worse?)'
[17:29:26] <ellyjones> cmasone: so I am hunting for a chromiumos-overlay revision that marks aa4761cc3647f2bf2e88f5de8e4d740973a1d0e8 as the chromeos-chrome revision?
[17:31:07] <cmasone> ellyjones: no, not so much...Chrome publishes "version specs", and we create ebuilds that point to each of these version specs as tehy are published -- one we validate them with the chrome PFQ
[17:31:15] <ellyjones> (unrelated: anyone know what 'missing /proc/device-tree/firmware on arm' is symptomatic of?)
[17:31:18] <cmasone> ellyjones: so, you can just go look at the chrome ebuilds we have
[17:31:39] <cmasone> ellyjones: and then look at revision history to see which one was stable at the time the failure startes
[17:31:43] <cmasone> started
[17:31:47] <ellyjones> ah, okay
[17:36:31] *** behdad has joined #chromium-os
[17:37:57] <ellyjones> cmasone: so the last 'marking ebuilds as stable' for chromeos-chrome before we started losing was 14.0.834.0
[17:37:58] *** SoulRaven has quit IRC
[17:39:26] <ellyjones> davemoore, you say?
[17:40:34] <ellyjones> hey, wait
[17:41:09] <ellyjones> ce8b40a33acf45061e08bf5a145f84bbdc648248 at 20100725-131543 marks 14.0.835.0 as stable, then 0717248ce653c2b07a551b0117de511f5fe562ff at 20110725-142620 marks 14.0.834.0 as stable??
[17:42:34] <ellyjones> that seems very odd
[17:43:02] <ellyjones> oh, my earlier failure is from USE=-device_tree
[17:45:39] <ellyjones> cmasone: please discuss time moving backwards?
[17:45:57] <cmasone> ellyjones: I 'unno :-)
[17:46:01] <cmasone> sosa: ^^^
[17:46:46] <sosa> crazies
[17:47:34] <ellyjones> sosa: what causes this madness
[17:48:35] <sosa> ellyjones:  the former is an alpha ebuild (TOT ebuild revving) and the latter is an rc...a build from DEPS
[17:48:57] <ellyjones> okay
[17:49:15] <ellyjones> I am still way out of my depth w.r.t debugging the chrome crash itself, which seems to be the main thing we care about
[17:49:56] <petermayo> Is the key thing to transfer  not the SVN commit numbers to a chrome expert?
[17:50:15] <petermayo> 93906 v 93917 v 93933 ?
[17:50:30] <petermayo> working ... ? ... broken?
[17:50:46] <cmasone> petermayo: ideall, yes, we would like to convert the chrome version strings to chrome SVN revisions
[17:51:00] <petermayo> or am I misreading CROS_SVN_COMMIT in the commitdiffs?
[17:52:00] <petermayo> are any of the MTV sheriffs online yet?
[17:52:11] <cmasone> petermayo: nope
[17:52:33] <petermayo> :-(
[17:52:38] *** kgunnit has left #chromium-os
[17:53:46] <cmasone> so, someone needs to revert simon's changes to get us back to the state we were at...
[17:54:36] *** wfrichar has joined #chromium-os
[17:54:37] *** ChanServ sets mode: +v wfrichar
[17:55:06] <petermayo> wfrichar appears to answer the call ...
[17:55:30] <wfrichar> I just got in. Looks like the build fell over again. :-P
[17:55:39] <petermayo> to repeat:  member:cmasone: so, someone needs to revert simon's changes to get us back to the state we were at...
[17:55:57] <cmasone> wfrichar: it looks like simon's changes at 7PM yesterday were the issue
[17:56:20] <wfrichar> How sure are we of that?
[17:56:57] <zbehan> can anyone help me clear an odd confusion? by running "emerge-$whicheverboard -pv ttf-fonts"
[17:57:02] <cmasone> wfrichar: well, it wasn't happening the build before that, and it's happened every time since.  And his were teh only changes :-)
[17:57:13] <wfrichar> sounds pretty sure.
[17:57:46] <wfrichar> I'm still scrolling back in the waterfall...
[17:57:55] <petermayo> there was also the ihf change ....
[17:58:04] <petermayo> 6587 is the first failure
[17:58:24] <petermayo> ... chromiumos/builders/x86%20generic%20pre%20flight%20queue/builds/6587
[17:58:40] <wfrichar> I see two changes with Simon's name on 'em.
[17:58:43] <cmasone> petermayo: that was a chrome-side change, which means that it hasn't percolated to our bots yet
[17:58:51] <cmasone> wfrichar: it's one of those, it's gotta be
[17:59:19] <wfrichar> If anyone knows which one, go ahead and revert.
[17:59:22] <petermayo> cmasone: right
[18:00:01] <petermayo> wfrichar:  at this point: I would say do both.  Haven't found them in gerrit yet.
[18:00:14] <wfrichar> Okay.
[18:00:30] <wfrichar> gimme a sec.
[18:00:37] <petermayo> found em ...
[18:00:45] <petermayo> I'll send the revert review to you?
[18:02:56] <zbehan> i don't think you need to send another review for reverting, just push the big revert button :)
[18:03:35] <petermayo> that creates a CL that reverts, it doesn't push it.
[18:03:41] <wfrichar> I found 'em too. petermayo, since you're looking at them, push the button.
[18:03:52] <petermayo> OK.
[18:03:57] <wfrichar> Yeah, then mark those new CLs as verified, +2, and hit the publish & submit button.
[18:04:24] <wfrichar> Add the reason why you're doing that, and email simon about it.
[18:04:33] <petermayo> Done:
[18:04:38] <wfrichar> thanks.
[18:05:04] <wfrichar> I thought we were supposed to have a non-PDT sherrif too?
[18:05:07] <petermayo> with a sherrif/multiple people around we have an opportunity to double-check someones work with the review workflow.
[18:05:11] <petermayo> She just left for lunch
[18:05:15] <wfrichar> ah.
[18:05:29] <petermayo> Taipei was also around, but are gone now.
[18:05:29] <wfrichar> and yet the build has been broken for 13+ hours.
[18:05:36] <wfrichar> Meh.
[18:05:37] <petermayo> You noticed.
[18:05:51] <wfrichar> Well, nothing's perfect.
[18:06:16] <wfrichar> And this does show that using the pfq and caching the previous builds lets most people continue working.
[18:06:25] <petermayo> Nope,  was scratching my head over a productive feedback mechanism, but I don't have a good one.
[18:06:39] <petermayo> (To previous comment)
[18:06:45] <wfrichar> me neither. some things are just hard to do.
[18:07:50] <wfrichar> Is it worth killing and restarting all those builds that we know will fail?
[18:08:10] <wfrichar> I think I'll restart the pfq, at least.
[18:08:15] <sosa> pfq is almost done?
[18:08:17] *** jrbarnette has quit IRC
[18:08:18] *** jrbarnette_ has joined #chromium-os
[18:08:24] *** jrbarnette has joined #chromium-os
[18:08:39] <petermayo> Almost ... it looks like it already knows it will fail.
[18:08:54] <sosa> yeah it's just saving the fail data
[18:08:55] <wfrichar> I stomped it.
[18:08:58] <sosa> *was*
[18:09:01] <wfrichar> sorry.
[18:09:05] <sosa> huzzah
[18:09:07] <sosa> i don't mind
[18:09:15] <wfrichar> we knew it would fail.
[18:09:24] <sosa> we dids
[18:10:06] <crosbot> tree became 'Tree is closed, might be fixed. Waiting on PFQ to be sure.'
[18:10:08] *** Keybuk has joined #chromium-os
[18:10:08] *** ChanServ sets mode: +v Keybuk
[18:10:22] <wfrichar> brb
[18:10:28] <petermayo> wfrichar:  Not only working, but commiting changes. Hopefully introducing no extra failures.
[18:13:17] *** jrbarnette_ has quit IRC
[18:19:14] <sosa> x86-generic full did not fail for good reasons :(
[18:19:37] <sosa> emerge: there are no ebuilds to satisfy "virtual/ttf-fonts" for /build/x86-generic/.
[18:21:19] <wfrichar> sosa: that showed up yesterday. Vince was looking at it.
[18:21:30] <zbehan> hah! so it's not juts me seeing this!
[18:21:41] <sosa> huzzah
[18:21:58] <sosa> actually ppl syncing and building from a fresh chroot would all see that
[18:22:04] <sosa> since it's not something the pfq caught
[18:22:23] <zbehan> well, the ebuild that creates the dependency has been added jul 6th
[18:22:36] <zbehan> but i can't trace where did ttf-fonts ever live
[18:23:20] <wfrichar> I suspect some completely unrelated ebuild that eventually depends on that through some weird chain of dependencies.
[18:23:44] <zbehan> that, or someone unmasked the defective one recently
[18:23:56] <wfrichar> my ebuild-fu is weak.
[18:24:38] <wfrichar> is there some mystical command that can print the dependency chain?
[18:24:47] <wfrichar> (no, of course not, that would be too easy)
[18:25:00] <cmasone> wfrichar: yes!
[18:25:01] <zbehan> emerge-$board --tree
[18:25:35] <wfrichar> ... no.
[18:25:53] <jrbarnette> equery-$board d <pkgname>
[18:26:16] <jrbarnette> only shows packages that name <pkgname> as a dependency directly
[18:27:05] <wfrichar> no luck there.
[18:27:10] <zbehan> well, emerge shows the whole trace leading to certain package (if used with --pretend/-p)
[18:27:27] <zbehan> should
[18:29:46] <wfrichar> Looking at the error message, it says "emerge: there are no ebuilds to satisfy "virtual/ttf-fonts" for /build/x86-generic/.
[18:29:46] <wfrichar> (dependency required by "x11-libs/libXft-2.2.0" [ebuild])
[18:30:21] <wfrichar> emerge-x86-generic libXft builds 2.1.14. There isn't a 2.2.0 AFAICT
[18:31:03] <zbehan> it picks 2.1.14 as the next best choice, because 2.2.0 is unsatisfied
[18:31:16] <wfrichar> But 2.1.14 builds just fine without ttf-fonts.
[18:31:33] <zbehan> yep, 2.2.0 was added jul 6th into portage-stable
[18:32:03] <cmasone> zbehan: but why are we even trying to pull in that newer version all of a sudden?  Why won't the old one satisfy our needs?
[18:32:07] <wfrichar> how come I don't see it in my workspace?
[18:32:56] <zbehan> i'm asking myself the same questions since sunday when i first saw this, and thought it has to be just me and my workspace (freshly created)
[18:33:36] <zbehan> wfrichar: does your x86-generic perhaps already have ttf-fonts installed?, how about emerge-x86-generic --unmerge -p ttf-fonts
[18:33:36] *** glotov has joined #chromium-os
[18:33:37] *** ChanServ sets mode: +v glotov
[18:33:53] <wfrichar> Couldn't find 'ttf-fonts' to unmerge.
[18:34:17] <zbehan> beats me then, i don't have an old chroot around to check this, in all of mine it's broken already
[18:35:31] <wfrichar>  /grumble
[18:36:39] <zbehan> well, time to dig through historic waterfall runs
[18:38:25] *** behdad has quit IRC
[18:38:59] <zbehan> hrm, the latest x86-generic-full run is happily building the old version
[18:39:23] <zbehan> wfrichar: in the chroot that works, can you check out src/third_party/portage-stable/x11-libs/libXft/ ?
[18:39:41] <wfrichar> what do you mean "check out"?
[18:39:48] <zbehan> look if it exists and has the new version
[18:39:52] <zbehan> ls -la, preferably
[18:40:06] <wfrichar> libXft-2.2.0.ebuild
[18:40:10] <cmasone> zbehan: check out is kind of an overloaded term in the revision control space :-)
[18:40:31] <zbehan> yeah, sorry about that :)
[18:40:43] <wfrichar> http://gerrit.chromium.org/gerrit/4729
[18:41:15] <wfrichar> no, sorry, wrong cut-n-paste
[18:41:19] <zbehan> wfrichar: how about emerge-x86-generic --info |grep OVERLAY
[18:42:04] <wfrichar> http://gerrit.chromium.org/gerrit/3712
[18:42:32] <wfrichar> PORTDIR_OVERLAY="/usr/local/portage/stable /usr/local/portage/chromiumos /home/wfrichar/trunk/src/private-overlays/chromeos-overlay /home/wfrichar/trunk/src/private-overlays/chromeos-partner-overlay /home/wfrichar/trunk/src/overlays/overlay-x86-generic"
[18:43:31] <zbehan> hrm, okay, mine has exactly that minus the private
[18:43:49] <wfrichar> Yeah, this is an internal checkout.
[18:44:12] <zbehan> yeah, those shouldn't affect anything, unless they contain a hidden copy of ttf-fonts (doubtfully)
[18:44:56] <zbehan> wfrichar: well, try a different trick: emerge-x86-generic -p "=libXft-2.2.0"
[18:45:12] <zbehan> it should tell you that it don't like it, and why exactly
[18:45:18] <wfrichar> emerge: there are no ebuilds to satisfy "virtual/ttf-fonts" for /build/x86-generic/.
[18:45:19] <wfrichar> (dependency required by "x11-libs/libXft-2.2.0" [ebuild])
[18:45:19] <wfrichar> (dependency required by "=libXft-2.2.0" [argument])
[18:45:58] <zbehan> er, ok, we already knew that, what's your portage version? (emerge --version)
[18:46:17] <wfrichar> I notice in the libXft-2.2.0.ebuild file, it says RDEPEND=virtual/ttf-fonts, and then DEPEND=$RDEPEND. That doesn't seem completely right.
[18:46:40] <wfrichar> 2.1.10.3-r1
[18:46:50] <zbehan> that's fine, it's just that building everything somehow skips the one which has unsatisfied dependencies, quietly
[18:47:17] <zbehan> only in old chroots, new chroots prefer to whine in the same situation, could be a portage feature recently turned on
[18:47:28] <wfrichar> the build command is build_packages --fact --nousepkg
[18:47:40] <wfrichar> s/--fact/--fast/
[18:47:42] <zbehan> yup, using binaries works just fine
[18:48:06] <zbehan> that's because no binary prebuilt is produced for the old version, so it only picks from a known good set
[18:48:49] <zbehan> wfrichar: could you pastebin someplace your complete emerge-x86-generic --info ?
[18:49:51] *** lipsinV2 has quit IRC
[18:50:27] <wfrichar> http://pastebin.com/Btj6n2Hk
[18:50:35] <wfrichar> line wraps aren't perfect.
[18:51:30] <petermayo> wfrichar:  PFQ has passed builTarget, and is into archiving ... time to reopen the tree?
[18:52:00] <wfrichar> I suppose. Do we not want to fix this new problem first?
[18:52:26] <petermayo> wfrichar: Oh, probably.  :-(
[18:52:33] <wfrichar> I'll update the status, though.
[18:53:10] <crosbot> tree became 'Tree is closed. Fixed one problem, still have one left.'
[18:53:41] <crosbot> tree became 'Tree is closed. Fixed one problem, still have one left (ttf-fonts dependency)'
[18:53:50] <petermayo> wfrichar:  the problem with being closed but changing:   still have "at least" one left.
[18:54:02] <wfrichar> good point.
[18:54:26] <crosbot> tree became 'Tree is closed. (Now working on ttf-fonts dependency)'
[18:57:16] <zbehan> wfrichar: hrm, i think the message was happening all the time but was choked by parallel_emerge, it just picks the next best version without saying anything
[18:57:44] <wfrichar> hmph.
[18:58:11] <wfrichar> Is that a workable solution? Do we NEED ttf-fonts?
[18:59:32] <zbehan> problem is, the same command downright fails now
[18:59:38] <wfrichar> which command?
[18:59:39] <zbehan> it doesn't just shrug it off and go on
[18:59:42] <zbehan> build_packages
[18:59:42] <wfrichar> oh, that.
[18:59:46] *** Adys has quit IRC
[19:00:05] <wfrichar> Right, but can we modify the libXft-2.2.0.ebuild to do without ttf-fonts?
[19:00:07] <zbehan> and i don't understand the change of behaviour, emerge --info is near identical between my and your
[19:00:31] <wfrichar> or is that the working builds are using old libXft?
[19:00:50] <zbehan> it's an upstream ebuild that we don't directly understand atm. just dropping the dependency is shooting in the dark, i'd prefer to just mask it, since we've been living on 2.1.x until now
[19:01:05] <wfrichar> Works for me.
[19:01:16] <zbehan> and ping marcheu who pushed it to also look at providing ttf-fonts
[19:01:23] <wfrichar> I was just typing that.
[19:01:47] <wfrichar> If you'll prepare a CL to mask it, I'll take a look at it.
[19:03:32] <marcheu> hmm so why is that thing breaking now?
[19:04:12] <zbehan> marcheu: it's been sorta broken since you pushed the updated ebuild, for some reason build_packages was skipping the new libXft because of unsatisfied dependencies and picking up the old one. until now.
[19:04:28] <marcheu> should I push the Xft 2.2.00 ebuild?
[19:04:40] <marcheu> 2.2.0 even
[19:04:53] *** Adys has joined #chromium-os
[19:04:57] <zbehan> marcheu: no, it already is pushed, in portage-stable, fft-fonts are missing
[19:05:11] <wfrichar> ttf-fonts
[19:05:18] <zbehan> er, that
[19:05:19] <marcheu> ah I have a change for that, we don't need that dependency
[19:05:51] <wfrichar> good. If you can push it Real Soon Now, that'll help with the build.
[19:05:59] <zbehan> marcheu: ok, that's probably going to be a better fix than masking the ebuild
[19:06:38] <marcheu> doesn't apply cleanly, but you can just remove the virtual/ttf-font line
[19:06:48] <marcheu> http://gerrit.chromium.org/gerrit/#patch,sidebyside,3882,1,x11-libs/libXft/libXft-2.2.0.ebuild
[19:07:31] <marcheu> which means you have to import libXft 2.2.0 in chromiumos-overlay I guess
[19:07:41] <wfrichar> Ah, right.
[19:08:07] <marcheu> I have a change for that
[19:08:19] <marcheu> should I push both?
[19:08:25] <wfrichar> yes, please.
[19:08:42] <marcheu> done
[19:09:56] <zbehan> marcheu: you should also uprev it to -r1, to make sure it's pulled in (or remove from portage-stable)
[19:10:23] <marcheu> okay let me prepare that
[19:11:23] <wfrichar> I see the change in gerrit, but it hasn't shown up in the buildbot waterfall. Is that normal?
[19:11:36] <wfrichar> Oh, there it is.
[19:11:37] *** Adys has quit IRC
[19:11:39] <wfrichar> darn lag.
[19:11:57] *** sergiu has joined #chromium-os
[19:11:57] *** sergiu has quit IRC
[19:11:57] *** sergiu has joined #chromium-os
[19:11:58] *** Adys has joined #chromium-os
[19:14:24] <ttuttle|work> argh
[19:15:33] <marcheu> wfrichar: http://gerrit.chromium.org/gerrit/4750
[19:16:08] <wfrichar> approved.
[19:16:19] <marcheu> pushed
[19:16:23] <wfrichar> thank you!
[19:16:37] <marcheu> sure, sorry about the breakage, even though I don't understant what happened :)
[19:17:00] <wfrichar> No problem. It only took three weeks to show up.
[19:17:18] <wfrichar> I'm going to open the tree again, so we can start breaking it immediately.
[19:17:54] <crosbot> tree became 'Tree is open (who knows? we might get lucky)'
[19:18:27] * ttuttle|work dives for gerrit to submit
[19:19:50] *** powderluv has joined #chromium-os
[19:19:50] *** ChanServ sets mode: +v powderluv
[19:22:46] <ferringb> zbehan: any issues w/ the depgraph from that baselayout change btw?
[19:24:22] *** saintlou has joined #chromium-os
[19:24:22] *** ChanServ sets mode: +v saintlou
[19:30:44] <zbehan> ferringb: nope, see the bug, everything reverted back to normal and working
[19:35:01] <zbehan> ferringb: it may be a false sense of security and i opened a bug for a better cleanup though, btw. i noticed that the glep you referenced is completely unimplemented
[19:36:15] <wfrichar> What happened to the build slaves?
[19:36:36] <wfrichar> Some of them have gone offline!
[19:36:51] <cmasone> wfrichar: they do that between runs...
[19:37:03] <cmasone> wfrichar: but it shouldn't be more thjan a minute or two
[19:37:05] <wfrichar> so they'll come back automagically?
[19:37:15] <cmasone> wfrichar: they should.  They get rebooted, I think
[19:37:20] <wfrichar> okay.
[19:37:22] <wfrichar> thanks.
[19:37:39] *** jrbarnette_ has joined #chromium-os
[19:37:42] <wfrichar> yep. there they go..
[19:37:48] <wfrichar> <whew>
[19:39:14] <ferringb> zbehan: there are days I think that's the natural outcome of gleps ;)
[19:40:31] *** jrbarnette has quit IRC
[19:41:32] <zbehan> ferringb: ah well, life is tough :) anyway i thought that glep seems an unnecessarily big hammer, this sounds like a feature that might be better off implemented outside portage, the eclass solution seems neat, clean and likely extensible enough for obscure configs
[19:41:58] <ferringb> zbehan: well, for cros this is fine
[19:42:08] *** jrbarnette_ has quit IRC
[19:42:34] <ferringb> zbehan: but for gentoo, keep in mind packages may be removed- meaning that one may want to prune the user/group modifications (or at the very least run refcounting on it in combination w/ a livefs scan to see if it can be pruned)
[19:43:00] <ferringb> zbehan: other angle there is that ldap configurations really aren't that uncommon w/ gentoo, so... complexity there is actually needed, if annoying
[19:43:04] <ferringb> glep died mainly since people got busy
[19:43:52] *** vlaviano has joined #chromium-os
[19:43:52] *** ChanServ sets mode: +v vlaviano
[19:46:38] <zbehan> ferringb: i haven't done any detailed analysis, so i won't comment, but sometimes a simpler feature would probably be better than no feature at all because there was no time to do the complex one :)
[19:47:06] * ferringb sure as hell ain't arguing that one ;)
[19:47:27] <ferringb> eclass is a nice step along that path either way, so that works
[19:47:33] <zbehan> ferringb: if only taking every ebuild's ugly postrm and postinst functions, putting them in one place (eclass) and inheriting them back, still better than a million scattered places
[19:48:26] * ferringb nods
[19:48:42] <ferringb> may look at scraping that out and feeding it back upstream actually, although it's not high on my priorities atm
[19:51:46] <zbehan> ferringb: well, i started the bug, and put it on my list, because the cros-sdk builder is danger of getting bit in the back by this again when the ebuild list shuffles next time, so i may at least clean up the pure upstream ebuilds that we use
[19:58:42] *** seanpaul has quit IRC
[19:59:03] *** D|sT has joined #chromium-os
[19:59:07] *** achuith has joined #chromium-os
[19:59:07] *** ChanServ sets mode: +v achuith
[19:59:10] *** seanpaul has joined #chromium-os
[19:59:11] *** ChanServ sets mode: +v seanpaul
[20:02:23] *** cooled_ has joined #chromium-os
[20:03:27] *** cooled has quit IRC
[20:04:23] *** BladeFreak has joined #chromium-os
[20:07:14] *** behdad has joined #chromium-os
[20:13:54] *** behdad has quit IRC
[20:18:04] *** jrbarnette has joined #chromium-os
[20:18:04] *** ChanServ sets mode: +v jrbarnette
[20:28:11] *** behdad has joined #chromium-os
[20:31:14] <zbehan> ferringb: heh, i bet you jinxed it by asking me if everything is ok with the baselayout dependency change :)
[20:43:55] <crosbot> tree became 'Tree is closed (Restarting stuck build, will be open again momentarily)'
[20:44:33] *** ihf has quit IRC
[20:44:45] <zbehan> wfrichar: bad news, looks like marcheu's fix helped, and my bug surfaced
[20:46:26] <marcheu> how is that bad news :)
[20:47:30] <zbehan> marcheu: ok, it's good news, followed by bad news :)
[20:47:41] <crosbot> tree became 'Tree is open'
[20:52:31] *** saintlou has quit IRC
[20:54:00] *** saintlou has joined #chromium-os
[20:54:00] *** ChanServ sets mode: +v saintlou
[20:54:13] *** rbyers has quit IRC
[20:54:19] *** saintlou has quit IRC
[20:58:00] *** rbyers has joined #chromium-os
[20:59:17] *** bponte has joined #chromium-os
[20:59:17] *** ChanServ sets mode: +v bponte
[21:02:08] *** bponte has quit IRC
[21:02:19] *** rharrison_chrome has quit IRC
[21:02:42] *** bpontes has joined #chromium-os
[21:02:43] *** ChanServ sets mode: +v bpontes
[21:09:27] *** saintlou has joined #chromium-os
[21:09:28] *** ChanServ sets mode: +v saintlou
[21:11:18] <ellyjones> crosbot: stat tree
[21:11:18] <crosbot> ellyjones: tree: Tree is open
[21:11:21] <ellyjones> excellent
[21:19:54] *** saintlou has quit IRC
[21:31:37] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "stumpy-binary" from eba2ee096481d80fa676a2b272b4cbdbb6639f2b: pfeldman at chromium dot org <pfeldman at chromium dot org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>, serya at chromium dot org <serya at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[21:32:21] <ellyjones> looking at it
[21:32:25] *** behdad has quit IRC
[21:32:47] <ellyjones> except that the waterfall page is lagging out, woo
[21:33:40] <ellyjones> umount: /b/cbuild/stumpy-private-bin/chroot/home/chrome-bot/trunk: device is busy.
[21:33:43] <ellyjones> hm.
[21:34:11] *** behdad has joined #chromium-os
[21:34:12] *** ChanServ sets mode: +v behdad
[21:34:42] *** saintlou has joined #chromium-os
[21:34:42] *** ChanServ sets mode: +v saintlou
[21:35:53] <ellyjones> I can't find any similar existing bug
[21:36:25] <ellyjones> aha, I bet it's 16651
[21:37:28] <crosbot> tree became 'Tree is open (ellyjones: stumpy-binary is crosbug.com/16651)'
[21:38:49] <ellyjones> a _lot_ of the bots are sick
[21:42:22] <zbehan> ellyjones: some could be just bumping into already resolved bugs
[21:43:40] <ellyjones> x86-generic-full failure is:
[21:43:41] <ellyjones> (sys-apps/baselayout-2.0.1-r219::chromiumos, ebuild scheduled for merge to '/build/x86-generic/') depends on
[21:43:44] <ellyjones>  (sys-apps/baselayout-2.0.1-r219::chromiumos, ebuild scheduled for merge to '/build/x86-generic/') (buildtime)
[21:43:47] <ellyjones> "wtf?"
[21:44:49] <zbehan> ellyjones: yep, i fixed that already
[21:45:05] <zbehan> ellyjones: all of the full builders are failing with this and won't be in the next run
[21:45:26] <ellyjones> ok, cool
[21:45:58] <zbehan> arm-tegra-binary fails for a different reason (u-boot)
[21:47:11] <zbehan> seaboard-gcc-4.6 is also stuck on circular dep, x86-generic-gcc-4.6 is stuck on ttf-fonts, which is also fixed
[21:47:29] <ellyjones> http://build.chromium.org/p/chromiumos/builders/arm%20tegra2%20binary/builds/6327/steps/cbuildbot/logs/stdio "Found nothing new to build, trying again later"
[21:48:40] <zbehan> so, only arm-tegra-binary and x86-chrome-preflight should be considered green, everything else is fixed bugs :)
[22:07:46] *** powderluv has quit IRC
[22:10:05] <ellyjones> uhoh, Humble Bundle 3 :(
[22:12:27] *** powderluv has joined #chromium-os
[22:12:27] *** ChanServ sets mode: +v powderluv
[22:16:15] *** JasonO-Web has joined #chromium-os
[22:18:16] <ellyjones> anyone know what 'chromiumos-sdk' is on the waterfall?
[22:18:37] <zbehan> ellyjones: someone's reading phoronix :)
[22:18:50] <zbehan> ellyjones: sdk is a builder of sdks
[22:18:57] <zbehan> (upcoming feature)
[22:19:00] <ellyjones> what is an sdk in this context?
[22:19:25] <zbehan> the chroot
[22:19:36] <ellyjones> so it's a prebuild chroot?
[22:19:40] <zbehan> yup
[22:26:57] *** xiyuan has joined #chromium-os
[22:26:57] *** ChanServ sets mode: +v xiyuan
[22:28:58] <crosbot> tree became 'Tree is closed (x86-generic pfq hung again, restarting)'
[22:29:03] *** JasonO-Web has quit IRC
[22:30:00] <crosbot> tree became 'Tree is open'
[22:30:54] *** Blinny has quit IRC
[22:31:51] *** patcito has joined #chromium-os
[22:42:04] *** rush2end_ has joined #chromium-os
[22:42:58] <steev_> is there a channel specific to chromium?
[22:43:39] *** vmil86 has quit IRC
[22:43:40] <steev_> apparently so
[22:43:46] *** rush2end has quit IRC
[22:43:51] *** rush2end_ is now known as rush2end
[22:45:04] <ellyjones> steev_: yes; #chromium
[22:45:05] <vlaviano> yeah, #chromium (though it sounds like you already figured that out)
[22:48:10] <steev_> yeah... not entirely what i was looking for, although maybe it is and i don't realize it.  I'm trying to find a url I found last night at home, that gives me the changelog between different builds
[22:49:49] <cmasone> steev_: of chromium?  They should be able to help you over there
[22:56:23] <msb___> gauravsh: you're going to git clone their repo, right?\
[22:56:30] <msb___> gauravsh: you're going to git clone their repo, right?
[22:56:58] <msb___> gauravsh: you're going to git clone their repo, right?
[22:57:24] <gauravsh> msb: yes
[22:59:08] *** msb___ has quit IRC
[23:00:19] *** rharrison_chrome has joined #chromium-os
[23:00:20] *** ChanServ sets mode: +v rharrison_chrome
[23:03:07] *** powderluv has quit IRC
[23:05:06] *** BladeFreak has quit IRC
[23:05:27] <zbehan> wfrichar, vlaviano: heads up, repushing a CL that was once reverted already (but shouldn't be problematic this time): http://gerrit.chromium.org/gerrit/4742 ; it will only affect arm-generic-full, if it gets reverted, the bot also has to be clobbered (arm-generic-full)
[23:07:24] <vlaviano> zbehan: ok, thanks for the warning
[23:07:35] *** msb__ has joined #chromium-os
[23:07:35] *** ChanServ sets mode: +v msb__
[23:09:18] <vlaviano> steev_: http://www.chromium.org/getting-involved/dev-channel/release-notes ?
[23:09:42] <vlaviano> nm, looking more closely, seems like they stopped updating that in 2009
[23:10:22] <vlaviano> but it has a link to a blog that contains similar info for current releases
[23:10:44] *** powderluv has joined #chromium-os
[23:10:44] *** ChanServ sets mode: +v powderluv
[23:19:19] *** rharrison_chrome has quit IRC
[23:20:30] *** fischman has quit IRC
[23:27:17] *** Ruetobas has quit IRC
[23:30:02] <steev_> vlaviano: actually i was looking for the actual changelog of chromium, i found it regardless, it's soemthing like http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/branches/782/src&range=90909:93151&mode=html
[23:30:57] *** Ruetobas has joined #chromium-os
[23:36:53] *** Styx has quit IRC
[23:43:30] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_kaen-binary" from 8f29e7f24e39d2d1b78caba7bda8fed778139300: Scott Zawalski <scottz at google dot com>)'
[23:44:33] <ellyjones> hmmm.
[23:44:54] <ellyjones> "Found nothing new to build, trying again later."
[23:45:36] <cmasone> ellyjones: yeah, I was just talking to scottz about that.  No idea what that means.  Maybe ping him?
[23:45:48] *** lipsinV2 has joined #chromium-os
[23:46:35] *** behdad1 has joined #chromium-os
[23:48:25] *** behdad has quit IRC
[23:48:48] *** rbyers has quit IRC
[23:49:14] <ellyjones> I just did
[23:50:31] *** sbyer_afk is now known as sbyer
[23:53:25] <ellyjones> hrm
[23:53:38] <ellyjones> so based on my not knowing what the hell, I am going to leave it closed
[23:53:57] <ellyjones> the blamelist for that build is empty, so something screwy is clearly going on
[23:54:22] <cmasone> ellyjones: perhaps update the status?
[23:54:25] <ellyjones> sure
[23:54:49] <ellyjones> I am about to turn into a pumpkin for a team dinner though
[23:54:57] <cmasone> ellyjones: I think it means "last time, I broke...and nothing new has happened.  So I'm still broken"
[23:55:04] <crosbot> tree became 'Tree is closed (ellyjones: empty blamelist for tegra2-binary; consulting with scottz)'
[23:55:04] *** stevenjb has joined #chromium-os
[23:55:04] *** ChanServ sets mode: +v stevenjb
[23:55:11] <ellyjones> why would it even retry?
[23:55:26] <ellyjones> or hm
[23:55:27] <ellyjones> "ERROR: Last build status was non-passing."
[23:55:35] <ellyjones> that looks bad
[23:55:38] <cmasone> yeah, that's what I'm talking about
[23:55:42] <ellyjones> hm
[23:55:45] <ellyjones> we're going to a team dinner
[23:55:48] <cmasone> it means "last time, it didn't pass, and I have nothing new..."
[23:55:48] * ellyjones evaporates
[23:56:03] <cmasone> vlaviano: wfrichar ^^^
[23:56:17] *** FusionX has quit IRC
[23:56:54] <wfrichar> oooh, is evaporation an option? I didn't know! See ya!
[23:58:20] *** FusionX has joined #chromium-os
[23:59:20] <crosbot> tree became 'Tree is closed (wfrichar: tegra2-binary U-Boot failure...)'





top