[00:08] 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] ToyKeeper: hmmm [00:15] 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] Anyway, it's already super-late here so I need to go to sleep [00:30] Goodnight o/ [03:57] anybody who knows how to fix the phablet-click-test-setup? === chihchun is now known as chihchun_afk [05:17] bzoltan: it's again the same remove basic_packages, since now they are from the overlay by default === chihchun_afk is now known as chihchun [07:17] bzoltan, good morning, is silo 17 ready for QA? [08:56] bzoltan, ping [09:21] bzoltan: hey, how's silo 17? [10:21] 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] Mirv: ACK, thanks :) === alan_g is now known as alan_g|lunch === MacSlow is now known as MacSlow|lunch [11:04] sil2100: oh, so someone still sets the overlay field without doing a reconfigure sometimes..... [11:04] so annoying [11:05] 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] 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] Mirv: the dashboard has the right info it seems [11:10] Mirv: if you look at the CI Train Dashboard, it will tell you when the silo is configured for the overlay PPA [11:10] sil2100: oh!! [11:11] sil2100: thanks to robru for that I guess! that should do it.. [11:11] Indeed :) Although we tend to forget about that anyway and blindly push the monkey button [11:11] the monkey team [11:20] If the trainguards had an LP team, our logo would be monkeys on the train in train-conductor hats [11:28] sil2100: exactly! :) [11:31] http://www.weirdasianews.com/2010/11/22/monkeys-appointed-stationmasters-japan/ [11:32] Oh god... [11:50] * sil2100 on lunch === MacSlow|lunch is now known as MacSlow === alan_g|lunch is now known as alan_g [13:46] bzoltan, the particular reason is that i didnt see it yet :) [13:46] not sure how to go about landing it though [13:46] ogra_: OK, that one I can accept [13:47] ogra_: SRU? LOL [13:47] haha [13:47] ogra_: My network here is "Foo Bar" and I have had problems pushing it to the device [13:47] well, we only need it in the PPAs i guess ... at least for a start [13:51] 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:51] Ubuntu bug 1450021 in Oxide "Crash in oxide::WebFrame::Destroy()" [Undecided,New] [13:58] rvr: *sigh* is it something new in the new oxide, or does it happen on the arale already? [14:06] sil2100: Already, AFAIK [14:06] sil2100: At least using image 26 [14:31] sil2100, when 17 lands, can you respin a new image? or you prefer to wait for oxide? [14:32] 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] sil2100, jibel the crash is in 1.7.3 as well [14:33] so 1.7.4 is better but not yet perfect [14:33] so we can land it and loo at the new crash [14:34] Then is oxide-qt still in sign-off? [14:34] the crash is not in 1.6 howver [14:34] pmcgowan, OK [14:34] If it is in sign-off, I wouold wait for oxide [14:34] (if, of course, it doesn't fail somehow else) [14:35] 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] jibel: Is it not a regression compared to 1.7.3. Signing off. [14:36] thanks [14:37] bzoltan: we need this approved :) https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/trunk-old-header/+merge/257684 [14:38] jibel, rvr: thanks guys :) [14:43] Ok, assuming all is ok [14:44] Overriding the unapproved branch [14:44] michi: disk space has been freed and jobs are running and succeeding again. [14:46] Ok, anything else we need? [14:47] I guess we have all packages we need [14:47] Let me kick a new image soon [14:48] sil2100, what did you decide on oxide jibel ? [14:48] pmcgowan: it has been published [14:48] oh too quick [14:48] thanks [14:48] davmor2 didn't see anything besides this crash which is not a regression :) [14:48] pmcgowan, landed as it not a regression in 1.74 compared to 1.7.3 [14:48] vg [14:49] sil2100: credit where credit is due rvr found the bug not me I just confirmed it [14:50] Indeed, sorry ;) [14:50] pmcgowan, jibel: once the PPA fully publishes the copies I'll kick a new image [15:17] 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] sil2100: pmcgowan: I'm reviewing the change, but then don't know what will happen once approved [15:18] doesn't affect anything else, as it was a missing device file only needed for hotspot [15:18] what should we do? [15:21] rsalveti, seems we can wait [15:23] abeato: pmcgowan: alright, approved the mr but didn't yet merge it, will merge once we can land new changes there [15:24] rsalveti, ok [15:27] rsalveti: hmmm, ok, so merging it in results in the change being released into the device tarball? [15:30] === IMAGE 187 building (started: 20150429-15:30) === [15:30] 187 ftw [15:31] sil2100: I think so, iirc they were all automatic [15:31] 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] josepht: Thank you very much for you help! [15:50] michi: my pleasure [15:55] o/ morning trainguards, looking for a silo for the request on line 30 [15:56] o/ [16:01] davidbarth: silo assigned, but both packages are already in silo 10 === chihchun is now known as chihchun_afk [16:29] Image rootfs just finished building [16:45] === IMAGE 187 DONE (finished: 20150429-16:45) === [16:45] === changelog: http://people.canonical.com/~ogra/touch-image-stats/187.changes === === chihchun_afk is now known as chihchun [16:48] * ogra_ wonders what that lxc-android-config is there [16:52] rsalveti, lxc-android-config 0.220 ? not 0.219vivid1 ? [16:52] ogra_, it was a fix for bug 1425880 [16:52] bug 1425880 in lxc-android-config (Ubuntu) "location settings doesn't persist upon reboot" [High,Confirmed] https://launchpad.net/bugs/1425880 [16:52] jibel, sure, not objecting that :) [16:53] * ogra_ needs to reboot ... silly arale killed my whole USB stack on the laptop [16:57] ogra_: right, was thinking about syncing that right once w opens [16:57] ogra_: but yeah, maybe it's just better to append vivid for all native packages === davidbarth is now known as dbarth === alan_g is now known as alan_g|EOD [17:32] pmcgowan: ubuntu-rtm/landing-003 silo has the back-port of the disappearing scopes fix :) [17:32] Once QA has some free cycles after RC testing I'll ask them to sign that off too [17:34] sil2100, ah forgot about that one [17:35] sil2100, problem is if we dont spin another image that missed the boat [17:35] pmcgowan: that's for the hotfix OTA [17:35] pmcgowan: it's from ubuntu-rtm :) [17:35] sil2100, oh right duh [17:36] pmcgowan: we already have the fix in vivid so no worries here [17:53] fginther, hey, does the artifact collection thingy (test*xml) look for the files recursively or shall I keep it flat? [17:58] Saviq, it should be recursive, though I can't find an example anywhere to prove it [17:58] Saviq, as long as the job has the right definition '**/test*xml' for example. [17:59] fginther, we'll have an example soon, then ;) [19:01] oSoMoN, Hi! [19:02] oSoMoN, I am seeing a white area at the bottom of fullscreen videos in portrait mode. [19:02] oSoMoN, its probably related to the "exit from fullscreen videos inside browser" change. [19:08] om26er, that was discussed here a few times at the sprint, i bet there is a bug for it [19:09] om26er, nope, it’s bug #1449188, and it’s fixed by oxide 1.7.4 [19:09] bug 1449188 in Oxide 1.7 "White bar when playing video fullscreen" [High,Triaged] https://launchpad.net/bugs/1449188 [19:09] ogra_, oSoMoN thanks both [19:14] 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] 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] oSoMoN, where to get 1.7.4 ? [19:19] there is a silo somewhere [19:20] om26er, in the overlay PPA [19:20] oSoMoN, aah I have 1.7.4 already [19:20] oSoMoN, 1.7.4-0ubuntu0.15.04.1~ppa1 [19:20] darn [19:20] let me try and reproduce that crash then [19:20] om26er, do you have a crash file? [19:22] oSoMoN, crash file is pretty useless atleast it looks like it [19:22] the oops is empty https://errors.ubuntu.com/oops/fdc517da-eea2-11e4-ac05-fa163e75317b [19:23] om26er, how big is the crash file? [19:25] oSoMoN, the previous one was very small, I deleted that. The one that is created now is 17 mbs [19:25] om26er, that’s much better, can you send it my way? [19:25] oSoMoN, I'll email that. In the meantime https://errors.ubuntu.com/oops/5cf46740-eea5-11e4-a5c5-fa163e4aaad4 [19:30] om26er, I can reproduce the crash, I’m getting a crash file here too [19:33] oSoMoN, hmm, hopefully it'll be a simple fix [19:34] 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] Ubuntu bug 1450021 in Oxide 1.7 "Crash in oxide::WebFrame::Destroy()" [Critical,Fix committed] [19:34] yup, confirmed [19:35] om26er, this will be fixed in oxide 1.7.6, which will be building in a PPA very soon [19:35] oSoMoN, thats good to know, thanks [22:26] om26er, ToyKeeper you guys still image testing? [22:27] pmcgowan: The regression suite for image 29 is about a third done. [22:28] However, the suite for 28 was about 85% done and I doubt we need to repeat all of it for 29. [22:30] 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] ToyKeeper, thanks [22:43] (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] oh [22:44] Probably related to the browser updates, but maybe not. Need to try it on older versions and other platforms to find out. [23:15] Might block the ability to buy apps at all. D'oh. [23:15] Will have more info in a bit.