[00:08] <ToyKeeper> Sorry, I can't discern any change from silo 6.  The scenario in the bug doesn't actually fail, and the silo doesn't appear to change the behavior.
[00:13] <sil2100> ToyKeeper: hmmm
[00:15] <ToyKeeper> I note it was tested originally on an image from a different server and different feed, with different numbering... and the two sets of images don't always behave the same.
[00:30] <sil2100> Anyway, it's already super-late here so I need to go to sleep
[00:30] <sil2100> Goodnight o/
[03:57] <bzoltan> anybody who knows how to fix the phablet-click-test-setup?
[05:17] <Mirv> bzoltan: it's again the same remove basic_packages, since now they are from the overlay by default
[07:17] <jibel> bzoltan, good morning, is silo 17 ready for QA?
[08:56] <jibel> bzoltan, ping
[09:21] <sil2100> bzoltan: hey, how's silo 17?
[10:21] <Mirv> sil2100: jibel: he's eating now, from what I've gathered they changed their approach (/MP) and need a rebuild which I just kicked since zoltan's build attempt failed as seen above
[10:21] <sil2100> Mirv: ACK, thanks :)
[11:04] <Mirv> sil2100: oh, so someone still sets the overlay field without doing a reconfigure sometimes.....
[11:04] <Mirv> so annoying
[11:05] <Mirv> so regardless if it's set or not, it still pretty much holds true that whenever doing a publish, always reconfigure + build watch_only first since there's no way to know
[11:05] <bzoltan> ogra_: is there a particulal reason why this MR was not laneded? It is a super simple fix and it does fix my problem :) https://code.launchpad.net/~bzoltan/phablet-tools/single_quotation_for_spaced_SSID/+merge/255500
[11:10] <sil2100> Mirv: the dashboard has the right info it seems
[11:10] <sil2100> Mirv: if you look at the CI Train Dashboard, it will tell you when the silo is configured for the overlay PPA
[11:10] <Mirv> sil2100: oh!!
[11:11] <Mirv> sil2100: thanks to robru for that I guess! that should do it..
[11:11] <sil2100> Indeed :) Although we tend to forget about that anyway and blindly push the monkey button
[11:11] <Mirv> the monkey team
[11:20] <sil2100> If the trainguards had an LP team, our logo would be monkeys on the train in train-conductor hats
[11:28] <Mirv> sil2100: exactly! :)
[11:31] <Mirv> http://www.weirdasianews.com/2010/11/22/monkeys-appointed-stationmasters-japan/
[11:32] <sil2100> Oh god...
[11:50]  * sil2100 on lunch
[13:46] <ogra_> bzoltan, the particular reason is that i didnt see it yet :)
[13:46] <ogra_> not sure how to go about landing it though
[13:46] <bzoltan> ogra_:  OK, that one I can accept
[13:47] <bzoltan> ogra_:  SRU? LOL
[13:47] <ogra_> haha
[13:47] <bzoltan> ogra_:  My network here is "Foo Bar" and I have had problems pushing it to the device
[13:47] <ogra_> well, we only need it in the PPAs i guess ... at least for a start
[13:51] <rvr> sil2100: I found an apparently new crasher for oxide. It is not happening in RTM/krillin. davmor2 confirmed, and oSoMoN and chrisccoulson are investigating https://bugs.launchpad.net/oxide/+bug/1450021
[13:58] <sil2100> rvr: *sigh* is it something new in the new oxide, or does it happen on the arale already?
[14:06] <rvr> sil2100: Already, AFAIK
[14:06] <rvr> sil2100: At least using image 26
[14:31] <jibel> sil2100, when 17 lands, can you respin a new image? or you prefer to wait for oxide?
[14:32] <sil2100> jibel: do we need a new oxide built? Since the reason it failed QA is because of the crash, which seems to be an old issue, right?
[14:33] <pmcgowan> sil2100, jibel  the crash is in 1.7.3 as well
[14:33] <pmcgowan> so 1.7.4 is better but not yet perfect
[14:33] <pmcgowan> so we can land it and loo at the new crash
[14:34] <sil2100> Then is oxide-qt still in sign-off?
[14:34] <pmcgowan> the crash is not in 1.6 howver
[14:34] <jibel> pmcgowan, OK
[14:34] <sil2100> If it is in sign-off, I wouold wait for oxide
[14:34] <sil2100> (if, of course, it doesn't fail somehow else)
[14:35] <jibel> rvr, if nothing else than this crash and it is not a regressino in 1.7.4 compared to 1.7.3, can you sign it off?
[14:36] <rvr> jibel: Is it not a regression compared to 1.7.3. Signing off.
[14:36] <jibel> thanks
[14:37] <sil2100> bzoltan: we need this approved :) https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/trunk-old-header/+merge/257684
[14:38] <sil2100> jibel, rvr: thanks guys :)
[14:43] <sil2100> Ok, assuming all is ok
[14:44] <sil2100> Overriding the unapproved branch
[14:44] <josepht> michi: disk space has been freed and jobs are running and succeeding again.
[14:46] <sil2100> Ok, anything else we need?
[14:47] <sil2100> I guess we have all packages we need
[14:47] <sil2100> Let me kick a new image soon
[14:48] <pmcgowan> sil2100, what did you decide on oxide jibel ?
[14:48] <sil2100> pmcgowan: it has been published
[14:48] <pmcgowan> oh too quick
[14:48] <pmcgowan> thanks
[14:48] <sil2100> davmor2 didn't see anything besides this crash which is not a regression :)
[14:48] <jibel> pmcgowan, landed as it not a regression in 1.74 compared to 1.7.3
[14:48] <pmcgowan> vg
[14:49] <davmor2> sil2100: credit where credit is due rvr found the bug not me I just confirmed it
[14:50] <sil2100> Indeed, sorry ;)
[14:50] <sil2100> pmcgowan, jibel: once the PPA fully publishes the copies I'll kick a new image
[15:17] <rsalveti> sil2100: pmcgowan: we got a small fix for the device tarball (creating a missing dev entry) that fixes the hotspot support for arale
[15:17] <rsalveti> sil2100: pmcgowan: I'm reviewing the change, but then don't know what will happen once approved
[15:18] <rsalveti> doesn't affect anything else, as it was a missing device file only needed for hotspot
[15:18] <rsalveti> what should we do?
[15:21] <pmcgowan> rsalveti, seems we can wait
[15:23] <rsalveti> abeato: pmcgowan: alright, approved the mr but didn't yet merge it, will merge once we can land new changes there
[15:24] <abeato> rsalveti, ok
[15:27] <sil2100> rsalveti: hmmm, ok, so merging it in results in the change being released into the device tarball?
[15:30] <imgbot> [15:30] <pmcgowan> 187 ftw
[15:31] <rsalveti> sil2100: I think so, iirc they were all automatic
[15:31] <rsalveti> sil2100: but even if not, in case we need to trigger a new device tarball, it will be included then as a side effect
[15:49] <michi> josepht: Thank you very much for you help!
[15:50] <josepht> michi: my pleasure
[15:55] <davidbarth> o/ morning trainguards, looking for a silo for the request on line 30
[15:56] <sil2100> o/
[16:01] <sil2100> davidbarth: silo assigned, but both packages are already in silo 10
[16:29] <sil2100> Image rootfs just finished building
[16:45] <imgbot> [16:45] <imgbot> [16:48]  * ogra_ wonders what that lxc-android-config is there 
[16:52] <ogra_> rsalveti, lxc-android-config 0.220 ? not 0.219vivid1 ?
[16:52] <jibel> ogra_, it was a fix for bug 1425880
[16:52] <ogra_> jibel, sure, not objecting that :)
[16:53]  * ogra_ needs to reboot ... silly arale killed my whole USB stack on the laptop
[16:57] <rsalveti> ogra_: right, was thinking about syncing that right once w opens
[16:57] <rsalveti> ogra_: but yeah, maybe it's just better to append vivid for all native packages
[17:32] <sil2100> pmcgowan: ubuntu-rtm/landing-003 silo has the back-port of the disappearing scopes fix :)
[17:32] <sil2100> Once QA has some free cycles after RC testing I'll ask them to sign that off too
[17:34] <pmcgowan> sil2100, ah forgot about that one
[17:35] <pmcgowan> sil2100, problem is if we dont spin another image that missed the boat
[17:35] <sil2100> pmcgowan: that's for the hotfix OTA
[17:35] <sil2100> pmcgowan: it's from ubuntu-rtm :)
[17:35] <pmcgowan> sil2100, oh right duh
[17:36] <sil2100> pmcgowan: we already have the fix in vivid so no worries here
[17:53] <Saviq> fginther, hey, does the artifact collection thingy (test*xml) look for the files recursively or shall I keep it flat?
[17:58] <fginther> Saviq, it should be recursive, though I can't find an example anywhere to prove it
[17:58] <fginther> Saviq, as long as the job has the right definition '**/test*xml' for example.
[17:59] <Saviq> fginther, we'll have an example soon, then ;)
[19:01] <om26er> oSoMoN, Hi!
[19:02] <om26er> oSoMoN, I am seeing a white area at the bottom of fullscreen videos in portrait mode.
[19:02] <om26er> oSoMoN, its probably related to the "exit from fullscreen videos inside browser" change.
[19:08] <ogra_> om26er, that was discussed here a few times at the sprint, i bet there is a bug for it
[19:09] <oSoMoN> om26er, nope, it’s bug #1449188, and it’s fixed by oxide 1.7.4
[19:09] <om26er> ogra_, oSoMoN thanks both
[19:14] <om26er> oSoMoN, when a video is being played in the browser and I try to open a new website in the same tab, browser disappears. poof!
[19:15]  * ogra_ blames jhodapp :P
[19:16] <oSoMoN> om26er, what version of oxide do you have on that device? if 1.7.3, can you upgrade to 1.7.4 and let me know whether you can still reproduce?
[19:16]  * jhodapp is innocent
[19:18] <om26er> oSoMoN, where to get 1.7.4 ?
[19:19] <ogra_> there is a silo somewhere
[19:20] <oSoMoN> om26er, in the overlay PPA
[19:20] <om26er> oSoMoN, aah I have 1.7.4 already
[19:20] <om26er> oSoMoN, 1.7.4-0ubuntu0.15.04.1~ppa1
[19:20] <oSoMoN> darn
[19:20] <oSoMoN> let me try and reproduce that crash then
[19:20] <oSoMoN> om26er, do you have a crash file?
[19:22] <om26er> oSoMoN, crash file is pretty useless atleast it looks like it
[19:22] <om26er> the oops is empty https://errors.ubuntu.com/oops/fdc517da-eea2-11e4-ac05-fa163e75317b
[19:23] <oSoMoN> om26er, how big is the crash file?
[19:25] <om26er> oSoMoN, the previous one was very small, I deleted that. The one that is created now is 17 mbs
[19:25] <oSoMoN> om26er, that’s much better, can you send it my way?
[19:25] <om26er> oSoMoN, I'll email that. In the meantime https://errors.ubuntu.com/oops/5cf46740-eea5-11e4-a5c5-fa163e4aaad4
[19:30] <oSoMoN> om26er, I can reproduce the crash, I’m getting a crash file here too
[19:33] <om26er> oSoMoN, hmm, hopefully it'll be a simple fix
[19:34] <oSoMoN> om26er, I suspect it’s a duplicate of https://bugs.launchpad.net/oxide/+bug/1450021 , I’ll be able to confirm in a minute
[19:34] <oSoMoN> yup, confirmed
[19:35] <oSoMoN> om26er, this will be fixed in oxide 1.7.6, which will be building in a PPA very soon
[19:35] <om26er> oSoMoN, thats good to know, thanks
[22:26] <pmcgowan> om26er, ToyKeeper you guys still image testing?
[22:27] <ToyKeeper> pmcgowan: The regression suite for image 29 is about a third done.
[22:28] <ToyKeeper> However, the suite for 28 was about 85% done and I doubt we need to repeat all of it for 29.
[22:30] <ToyKeeper> pmcgowan: Oh, just realized the tests for 29 are already trimmed down...  so it's about a third done, and the simple answer is "yes, still image testing".
[22:42] <pmcgowan> ToyKeeper, thanks
[22:43] <ToyKeeper> (have been a little side-tracked by bugs today, like we just found out the UI for adding a payment method is broken)
[22:43] <pmcgowan> oh
[22:44] <ToyKeeper> Probably related to the browser updates, but maybe not.  Need to try it on older versions and other platforms to find out.
[23:15] <ToyKeeper> Might block the ability to buy apps at all.  D'oh.
[23:15] <ToyKeeper> Will have more info in a bit.