[00:11:02] *** petermayo has joined #chromium-os
[00:11:03] *** ChanServ sets mode: +v petermayo
[00:19:50] <petermayo> adlr: ping(Do we know where the size issues seanpaul thought he might have a fix for have ended up?)
[00:26:16] <dianders> petermayo: I checked in a change that should get things compiling.
[00:27:00] <dianders> I can't do a verification that u-boot works on any of my boards (TPM failures on 2 of my boards and other failures on my seaboard).  Looking into those now so that I can see an actual booting u-boot.  Would be nice.
[00:27:08] <dianders> Fix is this one: http://gerrit.chromium.org/gerrit/#change,3894
[00:27:28] <dianders> ...if someone that has a working u-boot can patch that in and test it, I would much much much appreciate it.
[00:32:49] *** phil2 has quit IRC
[00:36:35] <adlr> petermayo: i don't know offhand
[00:36:50] <dianders> adlr: see my notes above..
[00:36:57] <adlr> yeah, just replying
[00:38:45] *** Transformer has joined #chromium-os
[00:39:51] *** Transformer has left #chromium-os
[00:43:28] *** TW1920 has quit IRC
[00:50:20] *** jrbarnette has quit IRC
[00:51:29] *** jrbarnette has joined #chromium-os
[00:51:30] *** ChanServ sets mode: +v jrbarnette
[00:55:26] *** vmil86 has quit IRC
[00:58:56] *** JasonO has quit IRC
[00:59:27] *** JasonO has joined #chromium-os
[00:59:27] *** JasonO has joined #chromium-os
[01:01:37] <dianders> adlr, petermayo, bfreed: I notice that arm_tegra2_binary at least compiled after my change.  :)
[01:02:40] <adlr> nice
[01:11:43] <adlr> kaen + aebl canaries succeeded
[01:12:50] <adlr> what are we waiting on for tree to open?
[01:12:55] <adlr> kliegs: ^^^
[01:13:37] <adlr> "arm tegra2 full" to pass build_packages?
[01:14:21] <bfreed> dianders: building u-boot now...
[01:14:50] <dianders> bfreed: Cool, thanks!  I think my seaboard is actually working now.  Not sure what was failing before, but might have just been user error (?).
[01:15:10] <dianders> bfreed: Going to try devboard, too...
[01:16:23] *** JasonO has quit IRC
[01:16:30] <dianders> MMC1 boot might not be working yet?  Not sure.
[01:19:29] <adlr> how can i compile w/ stack protector/stack guard?
[01:19:55] <marcheu> it's the default
[01:19:59] <adlr> hm
[01:20:14] <marcheu> you could add the option to make.conf, even though that would be overkill
[01:20:18] <marcheu> if you want to be 100% sure
[01:20:25] <adlr> i'm hanging in X, and gdb shows a corrupt stack when i attach
[01:20:41] <marcheu> on seaboard? yeah I saw that too
[01:20:56] <adlr> on kaen
[01:20:57] <marcheu> is it chrome crashing in some X lib?
[01:21:18] <marcheu> cause that's what I saw
[01:21:18] <adlr> my code (an input module) is running when it hangs
[01:21:32] <marcheu> ah ok then something else
[01:21:43] <marcheu> so the stack protector will make things crash for you
[01:21:57] <marcheu> but sooner than they would otherwise, so easier to track
[01:22:01] <marcheu> that's what it does
[01:22:33] <adlr> thanks
[01:22:36] <bfreed> dianders: criminy!  My u-boot fails for some unrelated reason: No rule to make target `chromeos_tegra2_kaen_developer_config'.
[01:23:00] <dianders> bfreed: I'll stop by and look.
[01:33:00] *** behdad1 has joined #chromium-os
[01:34:02] *** behdad has quit IRC
[02:09:14] *** powderluv has quit IRC
[02:09:49] *** lipsinV2 has joined #chromium-os
[02:20:07] <adlr> well that didn't last long
[02:20:44] <ferringb> back in the red?
[02:20:50] <adlr> yep
[02:20:52] <ferringb> heh
[02:22:05] <adlr> looks like mesa failed w/ some llvm related issue
[02:23:12] <thieule> adlr: there was an email about this failure, search your email for "mesa"
[02:23:21] <thieule> adlr: or i can forward you the email
[02:23:28] <adlr> oh
[02:23:46] <thieule> adlr: email forwarded
[02:24:16] <adlr> so i guess we clobber that bot?
[02:24:40] <thieule> adlr: i think so...only way to get it in a clean state
[02:28:52] *** jshin has quit IRC
[02:47:47] *** jrbarnette has quit IRC
[03:20:28] *** Trzaska has joined #chromium-os
[03:27:41] *** saintlou has quit IRC
[03:32:48] *** sergiu has quit IRC
[03:57:39] <adlr> I'm headed home for the night. Asian/Euro folks, feel free to handle the tree appropriately. If you get more llvm/mesa failures, you can clobber the bots and reopen
[03:57:56] <adlr> I'll be back to sheriff around 8:30am PT
[03:59:16] *** oc80z has quit IRC
[04:00:00] *** oc80z has joined #chromium-os
[04:08:03] *** achuith has quit IRC
[04:21:54] *** espeed has joined #chromium-os
[04:26:04] <sosa> pfq?
[04:29:01] *** powderluv has joined #chromium-os
[04:29:02] *** ChanServ sets mode: +v powderluv
[04:29:33] *** powderluv has quit IRC
[04:29:39] *** powderluv has joined #chromium-os
[04:29:39] *** ChanServ sets mode: +v powderluv
[04:35:38] *** Tukeke has joined #chromium-os
[04:35:41] *** Tukeke has quit IRC
[04:35:41] *** Tukeke has joined #chromium-os
[04:38:17] *** BladeFreak has quit IRC
[04:51:47] *** Tukeke has left #chromium-os
[04:52:39] *** espeed has quit IRC
[05:00:06] *** behdad1 has quit IRC
[05:00:50] *** behdad has joined #chromium-os
[05:00:51] *** ChanServ sets mode: +v behdad
[05:15:36] *** powderluv_ has joined #chromium-os
[05:15:41] *** ChanServ sets mode: +v powderluv_
[05:16:06] *** powderluv_ has quit IRC
[05:18:25] *** powderluv has quit IRC
[05:42:49] *** magn3ts has quit IRC
[05:50:30] <sosa> re-opened tree.  Arkaitzr's change to chromeos_startup was the culprit
[06:02:14] *** mascondante has joined #chromium-os
[06:06:50] *** yoshiki has quit IRC
[06:20:51] *** yusukes has quit IRC
[06:45:26] *** perezd has quit IRC
[06:47:51] *** behdad has quit IRC
[06:58:10] *** sadrul has quit IRC
[07:14:59] *** magn3ts has joined #chromium-os
[07:19:03] *** sadrul has joined #chromium-os
[07:27:01] *** powderluv has joined #chromium-os
[07:27:01] *** ChanServ sets mode: +v powderluv
[07:41:55] *** Styx has joined #chromium-os
[07:46:38] *** vmil86 has joined #chromium-os
[07:47:34] *** powderluv has quit IRC
[07:55:48] *** SoulRaven has joined #chromium-os
[08:24:10] *** e_t_ has joined #chromium-os
[09:06:18] *** jujugre has joined #chromium-os
[09:24:04] *** yoshiki has joined #chromium-os
[09:29:44] *** magn3ts has quit IRC
[10:12:45] *** ferringb has quit IRC
[10:18:52] *** echelog-1 has joined #chromium-os
[10:20:02] *** sygeek has joined #chromium-os
[10:20:58] *** rochberg_ has joined #chromium-os
[10:20:59] *** ChanServ sets mode: +v rochberg_
[10:21:24] *** benchan_ has joined #chromium-os
[10:21:25] *** ChanServ sets mode: +v benchan_
[10:21:50] *** benchan_ is now known as Guest98032
[10:25:33] *** FusionX has quit IRC
[10:25:33] *** benchan has quit IRC
[10:25:33] *** rochberg has quit IRC
[10:25:34] *** aaronp has quit IRC
[10:29:08] *** qzhou has joined #chromium-os
[10:34:53] *** sygeek is now known as FusionX
[10:35:37] *** ferringb has joined #chromium-os
[10:35:43] *** ferringb has quit IRC
[10:35:43] *** ferringb has joined #chromium-os
[11:02:10] *** ferringb has quit IRC
[11:03:31] *** patcito has quit IRC
[11:31:04] *** ferringb has joined #chromium-os
[11:31:24] *** jochen__ has quit IRC
[11:31:30] *** jochen__ has joined #chromium-os
[11:31:31] *** ChanServ sets mode: +v jochen__
[11:44:53] *** e_t_ has quit IRC
[12:24:58] *** aaronp has joined #chromium-os
[12:31:09] *** quannnum has quit IRC
[12:32:04] *** quannnum has joined #chromium-os
[12:51:49] *** Adys has joined #chromium-os
[13:58:47] *** petermayo has quit IRC
[13:58:57] *** flackr has joined #chromium-os
[13:58:57] *** ChanServ sets mode: +v flackr
[14:11:13] *** petermayo has joined #chromium-os
[14:11:13] *** ChanServ sets mode: +v petermayo
[14:34:31] <petermayo> Good Morning.
[14:36:00] *** TW1920 has joined #chromium-os
[14:41:26] *** SoulRaven has quit IRC
[14:49:17] *** dmazzoni has quit IRC
[14:59:09] *** rharrison_chrome has joined #chromium-os
[14:59:09] *** ChanServ sets mode: +v rharrison_chrome
[15:00:27] *** rbyers has joined #chromium-os
[15:00:39] *** ChanServ sets mode: +v rbyers
[15:05:28] *** sadrul has quit IRC
[15:14:39] *** leavittx has joined #chromium-os
[15:19:31] *** rharrison_chrome has quit IRC
[15:47:02] *** CrashTest_ has joined #chromium-os
[15:55:34] *** rbyers has quit IRC
[15:57:04] *** rbyers has joined #chromium-os
[16:28:30] *** behdad has joined #chromium-os
[16:28:30] *** ChanServ sets mode: +v behdad
[16:37:25] *** CrashTest_ is now known as CrashAFK
[16:50:37] *** CrashAFK is now known as CrashTest_
[16:58:00] <njw> aw, hell.
[16:58:55] <petermayo> njw:  :-(  you are fixing/reverting?
[16:59:23] <petermayo> njw:  it looks like you.
[16:59:27] <njw> I'm perplexed. The error I see is complaining that there's no 9999 ebuild. The commit I made was *creating* a 9999 ebuild.
[17:00:37] <petermayo> njw:  why is it looking in /home/chrome-bot/trunk/src?  seems unusual.
[17:01:09] *** CrashTest_ is now known as CrashAFK
[17:01:22] <petermayo> NM:  enter_chroot ....
[17:02:18] <njw> but I suppose absent any understanding of what's going on, I should revert that and get us back to the previous state.
[17:03:19] <petermayo> njw: thank you.
[17:03:39] <njw> done.
[17:04:36] <ellyjones> is there a way to get more history out of cautotest?
[17:06:11] <njw> hm. maybe I should have created a -0.0.1 as well as a -9999?
[17:07:34] <cmasone> njw: that sounds vaguely familiar
[17:07:58] <cmasone> njw: it's one of those bugs that is known, but only bites people creating new cros_workon packages, which is relatively rare
[17:08:02] <cmasone> njw: I think
[17:09:16] *** CrashAFK is now known as CrashTest_
[17:10:52] <njw> who would know for sure?
[17:10:52] <Guest98032> exit
[17:10:56] *** Guest98032 has quit IRC
[17:11:03] *** benchan has joined #chromium-os
[17:11:03] *** ChanServ sets mode: +v benchan
[17:11:22] <cmasone> njw: someone like davidjames, anush, or sosa.  Maybe also one of the newer build team people, like rcui or mtennant
[17:11:34] <cmasone> njw: none of whom are around :-)
[17:11:38] <cmasone> yet
[17:19:49] *** dmazzoni has joined #chromium-os
[17:22:35] <njw> where does the cbuildbot script live?
[17:22:49] <petermayo> chromite
[17:23:06] <petermayo> I know lots of it, but not the uprev pieve.
[17:23:07] *** lipsinV2 has quit IRC
[17:23:23] *** lipsinV2 has joined #chromium-os
[17:30:05] *** raymes has left #chromium-os
[17:32:58] <njw> okay, I think I made two mistakes.
[17:33:13] <njw> 1) not creating a 0.0.1 ebuild
[17:33:42] <njw> 2) having the arch keywords in my 9999 ebuild stable rather than unstable. (x86 vs. ~x86).
[17:34:25] *** oc80z has quit IRC
[17:35:12] *** oc80z has joined #chromium-os
[17:37:22] <cmasone> njw: that sounds true
[17:38:37] *** oc80z has quit IRC
[17:39:31] *** oc80z has joined #chromium-os
[17:39:45] *** saintlou has joined #chromium-os
[17:39:45] *** ChanServ sets mode: +v saintlou
[17:45:51] * adlr is back on the beat
[17:48:54] <ellyjones> Not even sha256 can save you from not knowing about message-extension attacks
[17:52:20] <adlr> does anyone here know who owns platform_ToolchainOptions, or in general how I would find that out?
[17:55:06] <ellyjones> git log on it?
[17:56:38] <adlr> good thinking
[18:01:34] *** wfrichar has joined #chromium-os
[18:01:35] *** ChanServ sets mode: +v wfrichar
[18:05:46] <cmasone> adlr: shit...is it failing somewhere?
[18:06:34] <cmasone> adlr: not that it's my test, just that we had a whole raft of issues around it last week
[18:07:45] *** FusionX has quit IRC
[18:08:03] <adlr> yes, it's flakey: http://cautotest/results/dashboard/netbook_ALEX/x86-alex-r13/bvt.html
[18:08:21] <adlr> i emailed asharif
[18:09:01] *** FusionX_ has joined #chromium-os
[18:10:07] *** FusionX_ is now known as FusionY
[18:10:36] *** BladeFreak has joined #chromium-os
[18:10:39] *** BladeFreak has joined #chromium-os
[18:10:45] *** jrbarnette has joined #chromium-os
[18:12:27] *** FusionY is now known as FusionX
[18:13:09] *** lipsinV2 has quit IRC
[18:13:28] *** lipsinV2 has joined #chromium-os
[18:17:56] *** jrbarnette_ has joined #chromium-os
[18:17:58] *** lipsinV2 has quit IRC
[18:19:57] <davidjames> njw: There's no need to create a 0.0.1 ebuild
[18:20:18] <davidjames> njw: The bot will create it for you. But there is a need to mark the 9999 as unstable. So that'
[18:20:29] <davidjames> njw: So that's what the bot was complaining about.
[18:21:02] *** seventh has quit IRC
[18:21:08] *** jujugre has left #chromium-os
[18:21:18] *** jrbarnette has quit IRC
[18:21:19] *** jrbarnette_ is now known as jrbarnette
[18:22:15] *** JasonO has joined #chromium-os
[18:28:37] <njw> ah, not finding a stable ebuild is just a warning, I see.
[18:31:21] <njw> I just added you to my CL's review set, if you wouldn't mind taking a look. I'd rather not break the build twice in the same morning.
[18:34:59] *** powderluv has joined #chromium-os
[18:34:59] *** ChanServ sets mode: +v powderluv
[18:40:43] *** leavittx has quit IRC
[18:57:55] *** sergiu has joined #chromium-os
[18:57:55] *** sergiu has joined #chromium-os
[19:13:09] *** leavittx has joined #chromium-os
[19:18:28] *** jshin has joined #chromium-os
[19:18:28] *** ChanServ sets mode: +v jshin
[19:21:23] *** perezd has joined #chromium-os
[19:27:36] *** JasonO has quit IRC
[19:31:54] *** Styx has quit IRC
[19:35:27] *** sadrul has joined #chromium-os
[19:35:39] *** ChanServ sets mode: +v sadrul
[19:37:40] *** jrbarnette_ has joined #chromium-os
[19:40:23] *** jrbarnette has quit IRC
[19:41:50] *** jrbarnette_ has quit IRC
[19:52:48] *** magn3ts has joined #chromium-os
[19:56:38] *** jrbarnette has joined #chromium-os
[19:56:39] *** ChanServ sets mode: +v jrbarnette
[20:09:43] <kliegs> ellyjones: crosbot is avoiding me :(
[20:10:22] *** quiccker has quit IRC
[20:11:23] <ellyjones> kliegs: :(
[20:12:32] <cmasone> I ain't seen crosbot 'round here for days
[20:16:27] *** kytibe has joined #chromium-os
[20:16:56] <adlr> yeah, this buildbot failure is odd. it's calling build_packegs w/ --nowithautotest, but it's trying to build autotest
[20:17:32] <petermayo> are there amny script changes that could be at fault?
[20:18:07] <ellyjones> adlr: so some package is depending on autotest?
[20:18:13] <ellyjones> equery-$board depends autotest
[20:19:29] <cmasone> if it's building chrome with USE=build_tests...that'd do it
[20:20:30] <adlr> hm, terry points out this could be the llvm+mesa deal
[20:20:43] <adlr> since mesa is a gl thing
[20:22:28] <ellyjones> the fact that 'make_dev_ssd.sh --help' does not explain what make_dev_ssd *does* is annoying
[20:24:47] <adlr> hm, i can't clobber that bot
[20:25:24] <ellyjones> ("it makes dev ssd, of course!")
[20:25:33] <adlr> i can only seem to clobber internal bots
[20:26:31] <cmasone> adlr: there's an internal view to the external tree
[20:26:41] <adlr> oh?
[20:27:59] <adlr> cmasone: can i get the link?
[20:33:03] <adlr> okay, i clobbered the arm-generic PFQ
[20:33:19] <cmasone> adlr: the arm-generic CHROME pfq?
[20:33:27] <adlr> hm
[20:33:43] <adlr> yes
[20:34:13] <adlr> also, on alex R13, we have a BVT issue. Chrome got a sig 11 during login_CryptohomeMounted
[20:34:54] <cmasone> adlr: so, chrome is segfaulting at some point before or after a user logs in?
[20:35:00] *** arun__ has joined #chromium-os
[20:35:58] *** arun_ has quit IRC
[20:36:00] <adlr> hm
[20:37:42] <petermayo> cmasone ... interesting, we have noticed this behavior locally here in wat on a chrome that was synced yesterday.
[20:38:00] <petermayo> I wonder if it is the same issue, and it is in USE=chromeos
[20:39:32] <adlr> hm, in a chrome log, i'm seeing ERROR:cryptohome_library.cc(235)] Received signal for unknown async_id 17
[20:40:11] *** rayon99 has joined #chromium-os
[20:40:23] *** rayon99 has quit IRC
[20:41:15] *** rcui has joined #chromium-os
[20:41:43] <cmasone> petermayo: USE=chromeos?
[20:41:53] <cmasone> petermayo: on what package?
[20:42:33] <cmasone> adlr: that is probably innocuous
[20:42:37] *** dtu has joined #chromium-os
[20:42:37] *** ChanServ sets mode: +v dtu
[20:43:05] *** rcui has quit IRC
[20:43:42] <cmasone> petermayo: are you talking about the Chrome GYP_DEFINES="chromeos=1"?  because a segfault in chrome could have been introduced by anyone on the chrome team proper as well.  Lots of things happen when chrome starts up, and then lots more things happen after login is triggered.
[20:43:43] <petermayo> cmasone: chrome
[20:44:09] <petermayo> cmasone: yes.
[20:44:11] <cmasone> petermayo: there is no USE=chromeos for the chrome package.  I suspect you're conflating USE flags with Chrome GYP_DEFINES
[20:44:21] <petermayo> cmasone: yes.
[20:45:04] <petermayo> cmasone: brain getting a little scrambled chasing down multiple issues in each of the trees.   Vacation tomorrow.
[20:45:09] <cmasone> petermayo: either way...yes, if someone who has seen this behavior and is in a position to debug it could investigate, that'd be a huge help.
[20:47:03] <petermayo> cmasone: looks like we ruled out our problem with segfaulting on login.  It looks like a local problem for us.
[20:47:27] *** rcui has joined #chromium-os
[20:47:30] <petermayo> just a little strange when the same problem happens in two places at the same time.
[20:48:05] <petermayo> Is there a team update this week?
[20:48:28] <cmasone> petermayo: peope here are asking that too
[20:48:37] <cmasone> I could swear it wasn't on calendar yesterday
[20:48:55] <petermayo> I could swear it wasn't there this morning.
[20:49:42] <cmasone> ...and now it's gone
[20:49:55] <petermayo> whee
[20:51:27] <adlr> do we get crash logs of chrome on the BVT?
[20:52:10] *** achuith has joined #chromium-os
[20:52:10] *** ChanServ sets mode: +v achuith
[20:56:27] *** CrashTest_ is now known as CrashDiet_
[20:57:54] *** JakeSays has quit IRC
[20:58:37] *** JakeSays has joined #chromium-os
[21:03:43] *** ChanServ sets mode: +v rcui
[21:05:57] <adlr> hm, i'm not sure what to do about this BVT chrome crash. I feel like we should try to gather the info we can and assign it to someone on the chrome team
[21:07:50] <petermayo> which builder are you seeing/calling the BVT?
[21:08:53] <adlr> all the info i have is an email; i'll forward
[21:08:58] <adlr> it's alex R13
[21:09:41] <adlr> petermayo: are you your IRC nick @ chromium.org?
[21:10:16] <adlr> ah yes
[21:10:23] <eggy> hey
[21:10:38] <adlr> petermayo: sent
[21:10:39] <adlr> eggy: hey
[21:11:43] <petermayo> adlr:  Yes.
[21:12:14] <eggy> what's the status on Chrome/14 going on the dev channel?
[21:17:49] *** powderluv has quit IRC
[21:17:57] *** powderluv has joined #chromium-os
[21:17:57] *** ChanServ sets mode: +v powderluv
[21:19:21] <adlr> petermayo: do you have an opinion on the BVT failure?
[21:20:18] <petermayo> adlr: not a good one.  I been reading too much into the builder going green.
[21:20:51] <adlr> it's odd that it would fail on R13
[21:20:55] <adlr> since that's relatively stable
[21:22:14] *** powderluv_ has joined #chromium-os
[21:22:15] *** ChanServ sets mode: +v powderluv_
[21:22:26] <petermayo> quite.
[21:22:36] <adlr> so, open the tree?
[21:22:51] <petermayo> sure.
[21:23:10] *** powderluv_ has quit IRC
[21:23:11] <petermayo> done
[21:23:19] <adlr> ok
[21:23:45] *** powderluv_ has joined #chromium-os
[21:23:45] *** ChanServ sets mode: +v powderluv_
[21:23:55] *** powderluv has quit IRC
[21:23:55] *** powderluv_ is now known as powderluv
[21:37:26] *** powderluv_ has joined #chromium-os
[21:37:27] *** ChanServ sets mode: +v powderluv_
[21:39:58] *** powderluv has quit IRC
[21:39:58] *** powderluv_ is now known as powderluv
[21:47:13] *** perezd has quit IRC
[21:50:21] <kliegs> adlr, bfreed, seanpaul, petermayo: I've got a change to commit that removes a file from the manifest.  Unfortunately this means the tree will go red the first time through as the PFQ's have trouble with it
[21:50:30] <kliegs> The second run of the bot will work after it fails, however
[21:50:34] <kliegs> Is now a good time to commit this?
[21:51:48] <adlr> hm, i think we are already waiting for some things to cycle green b/c of mesa/llvm
[21:52:14] <kliegs> adlr: no problem. its not critical - just removing a deprecated package
[21:52:20] <kliegs> can you please let me know a good time to commit?
[21:52:21] <adlr> kliegs: if you are around to help diagnose issues today, i could go for it
[21:54:09] <kliegs> adlr: Got ~2 more hours so it may just need to wait until tomorrow.  Change is just cleanup and no one will notice if its in or not so no pressure
[21:54:17] <adlr> i see
[21:54:26] <adlr> yeah, maybe wait until you'll be around a bit longer?
[21:54:33] <adlr> tomorrow morning?
[21:54:48] <adlr> i feel bad giving other sheriffs problems...
[21:55:03] <kliegs> adlr: Its actually held over from Friday, so you can blame those sheriffs :)
[21:55:18] <adlr> haha, i see
[21:55:20] <kliegs> Tomorrow is fine - yesterday was pretty brutal on you all anyways
[21:55:22] <adlr> well, back then it was a mess
[21:56:38] *** rbyers has quit IRC
[21:58:15] *** powderluv has quit IRC
[21:58:21] *** powderluv has joined #chromium-os
[21:58:22] *** ChanServ sets mode: +v powderluv
[21:58:27] *** ferringb has quit IRC
[21:58:27] *** ferringb has joined #chromium-os
[22:01:27] *** CrashDiet_ is now known as CrashTest_
[22:01:43] *** behdad has quit IRC
[22:03:29] *** rbyers has joined #chromium-os
[22:04:12] *** behdad has joined #chromium-os
[22:04:43] *** powderluv has quit IRC
[22:05:29] *** Adys has quit IRC
[22:07:16] <petermayo> perhaps pre-agreement from tomorrow's sheriffs would be better?
[22:07:53] <cmasone> if kliegs can't be around to shepherd it through today, then tomorrow sounds like the only option :-_
[22:07:56] <cmasone> :-)
[22:08:47] <kliegs> cmasone is right.  it doesn't really need much work shepherding but no point in committing and running.  and since its non-critical tomorrow is as good as tonight
[22:09:24] <kliegs> its really a minor change and the second build of it should work.  as long as the builds in a stable state and not in a "should go green" or "omgitsgreencommitnow zerg" it should be fine
[22:10:25] *** amiroot has joined #chromium-os
[22:11:30] <petermayo> aAre the prebuilts supposed to be accessible at http://chromeos-prebuilt/ ?
[22:17:07] <cmasone> looking
[22:17:21] <cmasone> wait...we compile shill?
[22:17:40] *** amiroot has quit IRC
[22:19:09] <cmasone> ok, this is my fault...let me figure out how to back out the change
[22:19:28] <petermayo> "this" = ...
[22:19:43] <cmasone> the tree closure
[22:19:44] <adlr> "revert patch set n"?
[22:20:29] <cmasone> adlr: done
[22:20:33] <adlr> thanks
[22:21:37] <adlr> tree is open
[22:21:50] <adlr> cmasone: thanks for your promptness
[22:22:51] <petermayo> adlr: clearly I'm done : I didn't notice the big red bar.   Guard it well.
[22:23:05] <petermayo> See Y'all in a couple of weeks.
[22:23:13] <adlr> have a good evening
[22:27:46] *** CrashTest_ is now known as CrashAFK
[22:30:58] * adlr steps out for a little while
[22:32:48] *** patcito has joined #chromium-os
[22:34:33] *** petermayo has left #chromium-os
[22:35:51] *** petermayo has joined #chromium-os
[22:36:01] *** petermayo has quit IRC
[22:42:49] *** vmil86 has quit IRC
[22:49:22] *** gspencer has joined #chromium-os
[22:49:22] *** ChanServ sets mode: +v gspencer
[22:50:26] <cmasone> bfreed: the arm-generic PFQ failure isn't me
[22:50:27] *** CrashAFK is now known as CrashTest_
[22:52:12] <dhendrix> hmmm
[22:52:25] <dhendrix> looks like flashrom :-/ that would be me. Checking into it now.
[22:52:51] <cmasone> hendrrIIIIIIIIX!!!!!
[22:53:01] <gauravsh> finish him
[22:55:57] <dhendrix> hmmm... in the arm_tegra2_binary build, it shows "Completed sys-apps/flashrom-0.9.3-r54 (in 0m9.0s)"
[22:59:16] <dhendrix> er--n/m, i see it now. I think I need to do a quick ebuild update to tell flashrom's Makefile to omit support for some devices.
[23:04:59] *** rbyers has quit IRC
[23:05:42] *** rbyers has joined #chromium-os
[23:06:58] <ojn> Damnit, accidentally submitted a patch on the closed tree.
[23:07:38] <cmasone> ojn: someone needs to patch gerrit :-/
[23:07:46] * cmasone puts finger aside nose
[23:10:17] <adlr> hey, did we ever fix the chrome autotest issue?
[23:10:29] * adlr losing track of all the issues
[23:14:49] *** flackr has quit IRC
[23:15:30] <dhendrix> build fix (hopefully): http://gerrit.chromium.org/gerrit/#patch,sidebyside,3962,1,sys-apps/flashrom/flashrom-9999.ebuild
[23:16:22] <adlr> dhendrix: did you try w/ an arm-generic build yourself?
[23:17:19] <dhendrix> adlr:  using a terga2_seaboard overlay
[23:17:43] <adlr> cool
[23:18:35] *** perezd has joined #chromium-os
[23:18:53] <dhendrix> adlr:  http://paste.flashrom.org/view.php?id=692
[23:19:09] <adlr> ah, re chrome+autotst, we suspect that's the mesa+llvm issue
[23:19:42] <adlr> cool
[23:20:11] <dianders> adlr: is there a way to fix autotest-tests?
[23:20:18] <dianders> I'm still getting compile-time failure...
[23:20:32] <adlr> dianders: can you try manually emerging llvm, mesa
[23:20:35] <adlr> then trying again
[23:20:36] <dianders> I'm syncing yet again just to make sure...
[23:20:40] <dianders> OK, I'll try that, too...
[23:20:56] <adlr> let me know how it goes
[23:21:12] <dianders> adlr: OK.  I'll validate first that I'm still seeing the issue, then try that...
[23:21:22] <adlr> dhendrix: let me know when that goes in
[23:21:41] <dhendrix> adlr:  I just hit the submit button
[23:21:49] <adlr> great
[23:22:01] <adlr> opposition to opening the tree, anyone?
[23:22:11] <adlr> (am i forgetting anything?)
[23:23:42] <adlr> tree is open
[23:24:56] <dianders> adlr: emerging mesa for host, or target?
[23:30:43] <adlr> target? both?
[23:31:49] * adlr steps out a bit
[23:32:15] <cmasone> dhendrix: the x86 pfq...is that failure also going to be fixed by your change?
[23:35:02] *** bfreed has quit IRC
[23:35:22] <cmasone> hm...never good when the only sheriff disappears...
[23:36:52] <dhendrix> cmasone:  hmmm...... didn't see that one coming. 1 min...
[23:39:16] *** rbyers has quit IRC
[23:49:55] <dhendrix> cmasone:  okay, i reproduced the failure on my end. looks like something may have gone wonky with my merge :-/ (I tried rebasing, and git had ran into an issue)
[23:56:35] <dhendrix> i can compile locally outside the chroot, so I'm guessing it's another ebuild issue.
[23:58:15] <davidjames> dhendrix: Maybe time to revert?





top