[00:44:46] <crosbot> tree became 'Tree is closed (Chrome ebuild is broken)'
[00:55:28] <crosbot> tree became 'Tree is closed (revert in for Chrome ebuild break)'
[00:59:05] *** D|sT has quit IRC
[01:01:16] *** sadrul has quit IRC
[01:19:41] *** sadrul has joined #chromium-os
[01:29:11] <crosbot> tree became 'Tree is open (Chrome ebuild past where it failed before)'
[01:34:20] *** D|sT has joined #chromium-os
[01:51:42] *** ferringb has quit IRC
[02:20:04] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "x86-alex-binary" from c1d5377d25be5dd9441894a958e7515587ced728: dtseng at chromium dot org <dtseng at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[02:20:04] *** bleung has left #chromium-os
[02:28:25] *** lipsinV2 has joined #chromium-os
[02:33:17] *** vmil86 has quit IRC
[02:36:39] *** patcito has quit IRC
[02:36:41] *** patcito_ has joined #chromium-os
[02:38:10] *** patcito_ is now known as patcito
[02:54:10] <crosbot> tree became 'Tree is open (Fix for cros_vm_lib pushed)'
[03:02:40] *** yusukes has joined #chromium-os
[04:58:38] *** bleung has joined #chromium-os
[04:58:38] *** ChanServ sets mode: +v bleung
[05:18:09] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "stumpy canary" from None: )'
[05:32:07] *** powderluv has joined #chromium-os
[05:32:08] *** ChanServ sets mode: +v powderluv
[05:33:06] *** powderluv has quit IRC
[05:33:14] *** powderluv has joined #chromium-os
[05:33:14] *** ChanServ sets mode: +v powderluv
[05:40:57] <crosbot> tree became 'Tree is open (Committed workaround hopefully for public key issue.)'
[05:51:41] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_kaen-binary" from d26eeb57120469ea8d5efd22661ed38ca2f105e3: mark at chromium dot org <mark at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[06:18:35] <crosbot> tree became 'Tree is open ("tegra2_kaen-binary" build already recovered from failure? -> kochi)'
[06:19:29] *** lipsinV2 has quit IRC
[06:27:24] *** SomKen has joined #chromium-os
[06:28:15] <SomKen> I have a bug in chromeos.  When I try to connect to a host, that I know the RSA key has changed, chromeos wont let me connect
[06:29:15] <SomKen> nvm
[06:29:16] *** SomKen has quit IRC
[06:43:44] *** SoulRaven has joined #chromium-os
[06:49:27] *** ihf has quit IRC
[06:49:27] *** marklarson has quit IRC
[06:49:49] *** tbarzic_ has quit IRC
[06:55:45] *** powderluv has quit IRC
[06:56:04] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "x86-zgb-binary" from 0397ad7ad2bf0596d142c7847b9e4063af1976dd: Zdenek Behan <zbehan at chromium dot org>)'
[07:02:11] *** lipsinV2 has joined #chromium-os
[07:25:38] *** vmil86 has joined #chromium-os
[08:04:59] <crosbot> tree became 'Tree is open (Flaky test, chrome sig 11)'
[09:03:11] *** Styx has joined #chromium-os
[10:10:11] *** cooled has quit IRC
[10:14:56] *** cooled has joined #chromium-os
[10:21:27] *** McMAGIC--Copy has quit IRC
[10:22:19] *** elly has quit IRC
[10:31:02] *** VictorBjelkholm has joined #chromium-os
[10:31:17] *** gsam_ has quit IRC
[10:35:09] *** gsam_ has joined #chromium-os
[10:35:10] *** ChanServ sets mode: +v gsam_
[10:38:16] *** patcito has quit IRC
[10:44:37] *** elly has joined #chromium-os
[12:26:20] *** McMAGIC--Copy has joined #chromium-os
[13:20:39] *** snickersnack has joined #chromium-os
[14:06:19] *** sadrul has quit IRC
[15:55:39] *** rharrison_chrome has joined #chromium-os
[15:55:39] *** ChanServ sets mode: +v rharrison_chrome
[16:03:59] *** sadrul has joined #chromium-os
[16:03:59] *** ChanServ sets mode: +v sadrul
[16:20:02] *** ScriptRipper has quit IRC
[16:31:16] <ellyjones> morning all
[16:33:03] *** cros_ has joined #chromium-os
[16:34:11] *** ScriptRipper has joined #chromium-os
[16:41:32] *** D|sT has quit IRC
[16:47:03] *** D|sT has joined #chromium-os
[16:47:34] *** D|sT has quit IRC
[16:59:12] *** D|sT has joined #chromium-os
[17:11:19] *** Styx has quit IRC
[17:14:50] *** Styx has joined #chromium-os
[17:17:21] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "x86-alex-binary" from 6b4fa88ebfd4779e1509317b7b09c56e8458f5d9: altimofeev at chromium dot org <altimofeev at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>, timurrrr at chromium dot org <timurrrr at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>, whesse at chromium dot org <whesse at chromium dot org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>)'
[17:32:43] *** grundler has joined #chromium-os
[17:32:43] *** ChanServ sets mode: +v grundler
[17:45:38] *** VictorBjelkholm has quit IRC
[17:45:43] *** jrbarnette has joined #chromium-os
[17:47:30] *** VictorBjelkholm has joined #chromium-os
[17:52:33] *** stevenjb has joined #chromium-os
[17:56:27] *** JasonO has joined #chromium-os
[17:56:27] *** JasonO has joined #chromium-os
[17:57:27] *** saintlou has joined #chromium-os
[17:57:27] *** ChanServ sets mode: +v saintlou
[17:57:38] *** saintlou has quit IRC
[18:04:04] *** jrbarnette_ has joined #chromium-os
[18:04:05] *** bpontes has joined #chromium-os
[18:04:06] *** ChanServ sets mode: +v bpontes
[18:07:42] *** jrbarnette has quit IRC
[18:07:42] *** jrbarnette_ is now known as jrbarnette
[18:18:14] *** rhashimoto has joined #chromium-os
[18:18:15] *** ChanServ sets mode: +v rhashimoto
[18:27:45] *** lipsinV2 has quit IRC
[18:27:59] <crosbot> tree became 'Tree is open (davemoore watching x86-alex-binary build for flakiness)'
[18:39:31] *** stevenjb has quit IRC
[18:42:06] *** BladeFreak has joined #chromium-os
[18:42:47] *** Keybuk has joined #chromium-os
[18:42:47] *** ChanServ sets mode: +v Keybuk
[18:45:12] *** stevenjb has joined #chromium-os
[18:45:12] *** ChanServ sets mode: +v stevenjb
[18:45:53] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_kaen-binary" from 4acdc2c8d4caecf7606db8af710366c1d6e28fe5: whesse at chromium dot org <whesse at chromium dot org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>)'
[18:53:52] <ellyjones> crosbot: sheriffs?
[18:53:53] <crosbot> ellyjones: sheriffs: davemoore, gabeblack, kochi, penghuang, falken
[18:54:20] <davemoore__> yeah
[18:54:30] <penghuang> hi
[18:54:32] <cros_> srao: ping
[18:55:30] <davemoore__> Looking for failure. Why does it claim that the tegra2_kaen_binary build failed, yet the current build claims to be running along fine?
[18:57:01] <davemoore__> or is it just old....and just closed from a build that failed hours ago, and has since stopped failing?
[18:57:31] <cros_> I want to run some autotests on my ARM platform. I notice for the package I'm interested in, chromeos-wm, in the ebuild there is a function for src_test() but it seems to skip building them for non-x86 platforms. Any idea why?
[18:57:37] <crosbot> tree became 'Tree is open (davemoore watching x86-alex-binary build for flakiness)'
[18:58:20] *** wfrichar has joined #chromium-os
[18:58:20] *** ChanServ sets mode: +v wfrichar
[18:58:23] <crosbot> tree became 'Tree is open'
[18:59:34] <ellyjones> the way that portage uses its own install stuff instead of an install target is odd
[19:00:02] *** sbyer has quit IRC
[19:00:39] *** sbyer has joined #chromium-os
[19:00:39] *** ChanServ sets mode: +v sbyer
[19:04:20] *** Sarten-X has quit IRC
[19:10:15] *** D|sT has quit IRC
[19:11:08] *** Sarten-X has joined #chromium-os
[19:13:34] *** ScriptRipper has quit IRC
[19:19:04] *** D|sT has joined #chromium-os
[19:24:57] *** dianders1 has joined #chromium-os
[19:27:24] *** ScriptRipper has joined #chromium-os
[19:27:39] *** ScriptRipper has joined #chromium-os
[19:29:14] *** VictorBjelkholm has quit IRC
[19:29:49] *** sergiu has joined #chromium-os
[19:29:50] *** sergiu has joined #chromium-os
[19:35:55] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_aebl-binary" from 7cf35f5edd32be422c2bc395a3c69d25a7643217: _third_party_ at chromium dot org, benjhayden at chromium dot org <benjhayden at chromium dot org@0039d316-1c4b-4281-b951-d872f2087c98>)'
[19:37:51] *** chocobo__ has joined #chromium-os
[19:37:52] *** ChanServ sets mode: +v chocobo__
[19:39:15] <crosbot> tree became 'Tree is closed (tegra2 failure -> davidjames)'
[19:44:37] <crosbot> tree became 'Tree is closed (cycling canaries -> davidjames)'
[19:46:55] <crosbot> tree became 'Tree is open'
[19:51:00] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "arm generic PFQ" from 9ee867e8a88f2cfcff4d422895e346c7fe31879c: _third_party_ at chromium dot org, jond at google dot com <jond at google dot com@4ff67af0-8c30-449e-8e8b-ad334ec8d88c>)'
[19:51:03] <satorux_> anyone familiar with the internal manifest git repository?
[19:51:20] <dianders1> satorux_: What question do you have?
[19:51:52] <satorux_> I'm following this instruction: http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/git-server-side-information#TOC-How-do-I-add-my-project-to-the-mani
[19:52:03] <dianders1> OK
[19:52:06] <satorux_> "git clone ssh://gerrit-int.chromium.org:29419/chromeos/manifest-internal.git" failed
[19:52:16] <dianders1> 1 sec...
[19:52:34] <satorux_> fatal: '/chromeos/manifest-internal.git': not a Gerrit project
[19:53:26] <dianders1> Worked for me.  Do you have access to the internal manifest?
[19:53:35] <satorux_> I suppose so
[19:54:16] <satorux_> I've added my pub key to gerrit-int.chromium.org
[19:55:24] <satorux_> "ssh -p 29419 gerrit.chromium.org gerrit ls-projects" returns me only playground/* repos
[19:55:49] <dianders1> OK, that sounds like you might not have access.  ?or somehow you're getting the wrong key...
[19:56:16] <satorux_> i see
[19:56:44] <satorux_> I guess I missed the step 10) at http://www.chromium.org/chromium-os/developer-guide/gerrit-guide
[19:57:08] <dianders1> OK, that could do it too.  Did that fix it?
[19:57:11] <ellyjones> why is arm-generic-pfq red?
[19:57:16] <satorux_> now trying
[19:57:54] <ellyjones> kernel failed to build
[19:57:58] <davemoore__> kernel compile fail
[19:57:59] <ellyjones> crosbot: sheriffs?
[19:58:00] <crosbot> ellyjones: sheriffs: davemoore, gabeblack, kochi, penghuang, falken
[19:58:06] <ellyjones> ah, davemoore__, one step ahead :P
[19:58:27] <davemoore__> looking....blame is on jond
[19:59:18] <ellyjones> I blame this: http://gerrit.chromium.org/gerrit/#change,5426
[19:59:30] <crosbot> tree became 'Tree is closed (davemoore -> looking into PFQ failures)'
[19:59:31] <ellyjones> the buildbot's blamelist is garbage
[19:59:41] <satorux_> dianders1: doing the step 10 worked! thank you for the help.
[19:59:42] <davemoore__> why is it there then?
[19:59:43] <ellyjones> the 'real' blamelist is at the bottom of this log: http://build.chromium.org/p/chromiumos/builders/arm%20generic%20PFQ/builds/306/steps/LKGMCandidateSync/logs/stdio
[19:59:59] <dianders1> satorux_: Great!  :)
[20:00:09] *** jrbarnette_ has joined #chromium-os
[20:00:25] <ellyjones> davemoore__: I don't know; I believe http://code.google.com/p/chromium-os/issues/detail?id=18140
[20:01:39] <davemoore__> sergiu: that's your change
[20:02:03] <sergiu> I
[20:02:05] <sergiu> I'm around
[20:02:07] <sergiu> taking a look
[20:02:14] <davemoore__> thx.
[20:02:15] *** jrbarnette has quit IRC
[20:03:36] <crosbot> tree became 'Tree is closed (sergiu-> looking into PFQ failures)'
[20:04:21] <sergiu> found the cause, reverting now
[20:04:43] *** JasonO has quit IRC
[20:05:09] *** JasonO has joined #chromium-os
[20:07:31] <sergiu> done
[20:11:15] <sergiu> sorry for that, didn't realise that it was dependent on one of the other commits :(
[20:12:51] *** achuith has quit IRC
[20:13:23] *** achuith has joined #chromium-os
[20:13:23] *** ChanServ sets mode: +v achuith
[20:16:24] *** achuith has quit IRC
[20:16:58] *** achuith has joined #chromium-os
[20:16:58] *** ChanServ sets mode: +v achuith
[20:20:40] *** jrbarnette has joined #chromium-os
[20:20:41] *** ChanServ sets mode: +v jrbarnette
[20:21:45] *** jrbarnette has quit IRC
[20:22:19] *** jrbarnette has joined #chromium-os
[20:22:19] *** ChanServ sets mode: +v jrbarnette
[20:22:20] *** patcito has joined #chromium-os
[20:24:33] <davemoore__> sergiu: should the tree be reopened?
[20:25:48] *** FusionX has quit IRC
[20:26:10] *** cooled_ has joined #chromium-os
[20:28:02] <sergiu> yeah, please do that, it seems that the build went ok
[20:28:34] *** FusionX has joined #chromium-os
[20:28:39] <sergiu> arm pfq is still building but it shouldn't fail if the others were ok
[20:28:40] *** cooled has quit IRC
[20:30:14] <sergiu> davemoore__, the tree should be ok to open now
[20:31:33] <crosbot> tree became 'Tree is open (sergiu-> fixed PFQ failures)'
[20:31:47] <sergiu> thank you
[20:33:34] *** rbyers_ has joined #chromium-os
[20:36:04] <Hexxeh> Anyone seen this error on the client with autoupdate before? Write was short: wrote 512 but expected to write 131072
[20:43:49] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2 seaboard full" from f01e9d0e5525b7d4f8e28a0b0aaccc1e35a27ae4: Gaurav Shah <gauravsh at chromium dot org>, _third_party_ at chromium dot org)'
[20:44:00] *** gnowen has joined #chromium-os
[20:45:38] <davemoore__> looking at fail
[20:47:09] <cmasone> davemoore__: oh, you're looking in the mirror again?
[20:47:28] *** dtu has joined #chromium-os
[20:47:28] *** ChanServ sets mode: +v dtu
[20:48:03] <davemoore__> cmasone: is that what you do all day? Lurk and then pounce?
[20:50:31] <ellyjones> Is cmasone immortal? Are his powers supernatural?
[20:50:58] <crosbot> tree became 'Tree is open (tegra2 seaboard full should cycle green with archive_build revert)'
[20:51:08] <cmasone> davemoore__: nah, I'm in a post-meeting, pre-lunch lull.
[20:51:11] <davemoore__> if he bleeds we can kill him
[20:53:36] *** gnowen has quit IRC
[20:56:09] <ellyjones> cmasone: do you have a moment to talk about strcmp vs strncmp?
[20:56:13] <cros_> Anyone know anything about the autotests?
[20:56:25] <ellyjones> cros_: that is a very broad question :P
[20:58:08] <cros_> I read through the information on the autotests and looked through the source but am confused. What I want to do is run one of the tests that are under the chromeos-wm package directory. The problem is I can't figure out how the python script autotests under the autotest directory invoke that test.
[20:58:34] <ellyjones> you want to un a unit test or an autotest?
[20:58:57] <cros_> ellyjones: That is probably the source of my confusion. You are right, the test in question seems to be a unit test.
[20:59:16] <ellyjones> is there a src_test function in the ebuild?
[20:59:38] <cros_> ellyjones: Yes there is. And I see an SConstruct file in the chromeos-wm directory that builds the unit tests.
[21:00:11] <cros_> ellyjones: I thought the autotests would somehow run those unit tests but I guess I am mistaken.
[21:00:13] <ellyjones> hrm
[21:00:45] <ellyjones> my flow in that situation is: FEATURES=keepwork emerge-$board $package ; ebuild-$board $(equery-$board which $package) test
[21:00:53] <ellyjones> that ought to do it on x86
[21:01:21] <cros_> ellyjones: So build_packages won't build the unit test?
[21:01:32] <ellyjones> I don't know
[21:02:58] <cros_> ellyjones: How do you run those unit tests then? And to confirm, autotests are different than these tests?
[21:03:10] <ellyjones> autotests are end-to-end tests, mostly
[21:03:28] <ellyjones> you should end up with some binaries in /build/$board/tmp/portage/.../$package
[21:03:31] <ellyjones> which you can run
[21:04:17] <cros_> ellyjones: Thanks, I just found some docs on the website relating to unit tests so let me pour over them and see what I end up with.
[21:04:53] <ellyjones> cool
[21:07:34] <sergiu> cros_, ellyjones running the unit tests should work as well with FEATURES=test emerge-$board $package
[21:08:03] *** cros__ has joined #chromium-os
[21:08:42] *** cros_ has quit IRC
[21:09:20] <cros__> sergiu: That sounds right. I'm not as familiar with portage as I'd like so I don't know all the FEATURES you can specify. Do you know if build_packages will build the tests?
[21:10:32] <sergiu> cros__, it should, ./build_packages --help shows
[21:10:39] <sergiu>   --[no]withtest:  Build packages required for testing. (default: true)
[21:10:46] <sergiu> so it should be enabled by default
[21:11:46] <cros__> sergiu: Hmm, ok, I definitely don't see the test binaries anywhere but let me try again.
[21:12:01] <quiche> i could easily be wrong here, but i think "--withtest" controls whether or not dependent packages are built -- not whether the unittests are built and run.
[21:12:39] <quiche> (dependent -> packages required for testing)
[21:13:05] <quiche> i use FEATURES=test to build & run the unittests
[21:13:07] <sergiu> cros__, I run the tests by appending FEATURES=test to the emerge command line, not by searching some test binaries
[21:13:27] <cros__> quiche: That's what I thought based on comments in the build_packages script.I guess I could do FEATURES=test build_packages ...
[21:14:14] <cros__> sergiu: I typically build using build_packages since I don't modify any packages but I'll take anything that works.
[21:14:25] <sergiu> here's my flow:
[21:14:43] <sergiu> for example for the crash-reporter module
[21:14:50] <quiche> one pitfall to keep in mind is that tests won't be run if you build for a different board. (pretty obvious if the processor is different. but even board differences seem to matter, IME.)
[21:15:12] <sergiu> ./build_packages --board=$BOARD --withtest
[21:17:15] <sergiu> FEATURES=test emerge-$BOARD crash-reporter
[21:17:40] <sergiu> that would run the unittests
[21:18:15] <cros__> sergiu: Build or run the unittests? I'm cross-compiling for an ARM platform.
[21:18:24] <sergiu> that does both
[21:18:33] <sergiu> builds them first and them runs them
[21:18:49] <cros__> sergiu: I'm guessing you are building on your target device?
[21:18:53] <sergiu> I'm not sure how you could _only_ run them
[21:19:35] <sergiu> well, you specify the target device using the appropriate emerge version (e.g. emerge-x86-generic)
[21:19:49] <sergiu> in your case emerge-arm-generic maybe
[21:20:28] <cros__> sergiu: I'm just not sure how it will run the tests on my target platform which is different than where I am building but maybe it operates similar to run_remote_tests with autotests.
[21:22:21] <sergiu> I think I understand what you mean ... I'm not sure if the unit tests are built (or able for that matter) to test platfrom specific aspects
[21:22:44] <sergiu> I think that's left for the autotests, but I don't have enough knowledge about that
[21:22:47] *** rbyers_ has quit IRC
[21:24:08] *** rbyers_ has joined #chromium-os
[21:34:32] *** rbyers_ has quit IRC
[21:35:31] *** rbyers_ has joined #chromium-os
[21:38:56] *** petermayo has joined #chromium-os
[21:38:57] *** ChanServ sets mode: +v petermayo
[21:49:52] *** achuith has quit IRC
[21:49:59] *** achuith has joined #chromium-os
[21:49:59] *** ChanServ sets mode: +v achuith
[21:50:02] *** achuith has quit IRC
[21:50:12] *** achuith has joined #chromium-os
[21:50:12] *** ChanServ sets mode: +v achuith
[21:58:00] *** Lisa3 has joined #chromium-os
[22:00:24] *** powderluv has joined #chromium-os
[22:00:24] *** ChanServ sets mode: +v powderluv
[22:01:37] * powderluv sheriff gabeblack is out sick. tbroch/powderluv will stand in for him
[22:15:04] <cros__> ellyjones: You mentioned earlier that you run an emerge and then an ebuild command like this: FEATURES=keepwork emerge-$board $package ; ebuild-$board $(equery-$board which $package) test
[22:15:29] <cros__> ellyjones: I thought the ebuild becomes redundant there?
[22:15:44] <cros__> ellyjones: Ignoring the fact that you are building the tests there.
[22:16:09] <sosa> is there an "easy" method to extra a kernel from a recovery image?
[22:16:23] <ellyjones> cros__: dunno :)
[22:17:05] <cros__> ellyjones: I think I get it based on what others have said. sergiu mentioned you can do FEATURES=test emerge ... but you are essentially doing the same by running ebuild ... test
[22:18:15] <ellyjones> cool
[22:19:16] <davidjames> tbroch, powderluv: x86 mario canary is about to fail due to sig11 in tests
[22:20:50] <sosa> davidjames:  i thought derat committed a workaround for that?
[22:22:01] <davidjames> sosa: Yeah he did. This looks like a different crash though, a sig11 in supplied_chrome. Still a flaky failure but maybe a different flaky failure
[22:22:21] <sosa> ah
[22:23:01] *** SoulRaven has quit IRC
[22:23:31] <ellyjones> landing my minijail rewrite... higher probability of loss :)
[22:23:59] <davidjames>  davemoore, gabeblack, kochi, penghuang, falken: could you look into the supplied_chrome crash on x86-mario canary?
[22:29:15] <quiche> cros_: if you're building on a different platform that you want to test on, then you probably want to use FEATURES=keepwork or FEATURES=noclean, and then copy the unittest binaries over to the target device. (at least, i don't know of a better way myself.)
[22:29:45] <crosbot> tree became 'Tree is open (segv in supplied_chrome on x86-mario canary -> sheriffs)'
[22:30:31] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2 PFQ" from e173076a6c88b21612512d89d4bae642c8bee616: jvoung at google dot com <jvoung at google dot com@fcba33aa-ac0c-11dd-b9e7-8d5594d729c2>)'
[22:33:19] <crosbot> tree became 'Tree is closed (tegra2 PFQ ... investigating -> tbroch)'
[22:35:08] *** JasonO has quit IRC
[22:37:35] <cmasone> this looks like a failure that should be escalated to a trooper asap
[22:40:30] <ellyjones> ERROR: Cannot find commit id for /home/chrome-bot/trunk/src/third_party/chromiumos-overlay/chromeos-base/system_api/system_api-9999.ebuild
[22:40:33] <ellyjones> hmm.
[22:40:44] <cmasone> sosa: ^^^
[22:41:02] <cmasone> is this the "I can't deal with a 9999 ebyuild for a package that has no 0.0.1 ebuild
[22:41:06] <cmasone> " thing?
[22:41:12] <ellyjones> crosbot: troopers?
[22:41:13] <crosbot> ellyjones: troopers: djmm, scottz, bradnelson, maruel (EST), kliegs (EST)
[22:45:01] <satorux_> hmm
[22:45:03] <cmasone> davidjames: can you help tbroch figure this out?
[22:45:12] <satorux_> system_api-9999 was added by me
[22:45:18] <satorux_> anything went wrong with it?
[22:45:39] *** saintlou has joined #chromium-os
[22:45:41] *** ChanServ sets mode: +v saintlou
[22:45:53] <ellyjones> did you also add an -0.0.1?
[22:46:32] <satorux_> no
[22:46:45] <satorux_> i thought it'll be automatically handled by the commit-bot
[22:46:52] <satorux_> but I seemed to be wrong...
[22:47:01] <powderluv> satorux_: it should be added
[22:47:12] <satorux_> okay, then i'll add it asap
[22:48:05] <satorux_> the file name should be system_api-0.0.1-r1.ebuild ?
[22:48:08] <powderluv> satorux_:
[22:48:16] <powderluv> it needs to be in the manifest first
[22:48:48] <powderluv> lets revert the system_api ebuild CL for now
[22:48:57] <powderluv> and land it again once it is added in the manifests
[22:48:57] <satorux_> okay
[22:49:06] <satorux_> I have a change to add it to manifest
[22:49:06] <powderluv> tbroch is sending the revert your way
[22:49:14] <satorux_> didn't know it had to be checked in earlier
[22:49:20] <powderluv> yeah
[22:49:24] <davidjames> satorux_: Yup we check to make sure you do that :)
[22:49:43] <powderluv> davidjames: maybe we should warn that it is missing
[22:49:48] <satorux_> adding a repo is trickier than i thought
[22:49:52] <powderluv> so it easy to debug
[22:49:53] *** sevich_ has joined #chromium-os
[22:50:04] <davidjames> powderluv: It does warn right there, that's the failure :)
[22:50:23] <powderluv> satorux_: maybe we can use your help to clean up the "how to add a repo" docs
[22:50:24] <davidjames> powderluv: The fail was added in intentionally so people know why their cros-workon ebuild isn't getting rev'd :)
[22:50:25] <powderluv> :)
[22:50:42] <satorux_> I'll write up something once I go through all the steps
[22:50:53] *** jennytalia has joined #chromium-os
[22:50:56] <davidjames> satorux_: Yeah thanks, you're not the only person to hit this
[22:51:04] *** sevich_ has quit IRC
[22:51:10] <powderluv> sounds good. thanks. probably just update the docs on chromium.org
[22:51:34] *** sevich has joined #chromium-os
[22:52:04] <cmasone> tbroch: man, why doesn't my irc client recognize your nick...
[22:53:15] <gauravsh> heh
[22:53:20] *** tbroch has joined #chromium-os
[22:53:21] *** ChanServ sets mode: +v tbroch
[22:53:32] <cmasone> tbroch: oh, hey, buddy :-)
[22:53:47] <satorux_> so the right steps would be 1) add a line to oldlayout.xml in both internal and external manifest repos. 2) add 9999 and -0.0.1-r1.ebuild to chromiumos-overlay.git? do I need to do something else?
[22:55:36] <sevich> Hi! I'm launching Chromium OS image with the script /cros_start_vm.  I was wondering if there is an easy way to modify kernel command line? Or I have to setup Dev Server and update image every time I want to change command line?
[22:56:50] <crosbot> tree became 'Tree is closed (revert merged should cycle green -> tbroch)'
[22:57:10] <tbroch> hi cmasone :)
[22:57:40] *** jennytalia has left #chromium-os
[22:58:48] <sevich> ok. Maybe it is better to post this question to the mailing list =)
[23:00:13] <satorux_> hmm, looking at http://gerrit.chromium.org/gerrit/#change,2957, 0.0.1 ebuild doesn't seem to be necessary
[23:01:31] <satorux_> gestures-0.0.1-r1.ebuild was created by the commit bot
[23:02:26] <satorux_> I guess what I was missing was to update oldlayout.xml earlier than addding 9999.ebuild?
[23:04:27] <davidjames> satorux_: Update oldlayout.xml first, then the 9999 ebuild
[23:04:41] <satorux_> so 0.0.1 ebuild is unnecessary, right?
[23:04:49] <davidjames> satorux_: Yup
[23:04:54] <satorux_> okay
[23:05:04] <satorux_> thanks
[23:13:42] *** Lisa3 has left #chromium-os
[23:13:44] <crosbot> tree became 'Tree is open (revert fixed PFQ failures -> tbroch)'
[23:15:06] *** rharrison_chrome has quit IRC
[23:17:51] *** sevich has quit IRC
[23:20:27] <cmasone> thx
[23:20:41] <cmasone> whoops
[23:27:05] <redpig> they're on to you. run!
[23:35:25] *** rbyers_ has quit IRC
[23:37:11] <satorux_> I'm about to re-land system_api-9999.ebuild
[23:37:41] <satorux_> oldlayout.xml in both the internal and external repos has been updated, so it should work out this time...
[23:38:04] *** rbyers_ has joined #chromium-os
[23:42:41] *** JasonO has joined #chromium-os
[23:42:42] *** JasonO has joined #chromium-os
[23:44:38] <satorux_> landed. fingers crossed
[23:44:45] <satorux_> ping me if anything goes wrong again
[23:47:47] *** saintlou has quit IRC
[23:48:14] <crosbot> tree became 'Tree is closed (Automatic: "cbuildbot" on "tegra2_arthur canary" from None: )'
[23:48:47] <satorux_> ugh, did my change break it?
[23:50:20] <satorux_> what's tegra2_arthur canary? I don't see it in the waterfall page
[23:51:19] <tbroch> http://chromeos-botmaster.mtv.corp.google.com:8026/builders/tegra2_arthur%20canary
[23:51:48] <crosbot> tree became 'Tree is closed (tbroch -> investigating "cbuildbot" on "tegra2_arthur canary" from None: )'
[23:52:35] *** petermayo has quit IRC
[23:54:56] *** saintlou has joined #chromium-os
[23:54:56] *** ChanServ sets mode: +v saintlou
[23:55:12] *** cros__ has quit IRC





top