[02:10] <imgbot> [03:40] <imgbot> [03:40] <imgbot> [08:10] <Mirv> not sure if it makes sense to have meetings this week without jib_el and sil, but today I need to jump towards dentist part 1 anyway now.
[08:10] <Mirv> let's have meetings if there's a specific issue that's worth chatting about in a hangout
[08:11] <ogra_> +1
[08:11] <ogra_> popey, davmor2 ^^^ anything to discuss this morning ?
[08:20] <davmor2> ogra_: not sure what popey's responce was, I'm assuming that the new oxide finally built and is in the image right?
[08:20] <ogra_> davmor2, http://people.canonical.com/~ogra/touch-image-stats/rtm/270.changes
[08:22] <davmor2> ogra_: in that case as far as I know we are retesting the web based subsection of the regression suite and once that passes letting you know
[08:24] <popey> ogra_: davmor2 +1
[08:24] <ogra_> is that davmor3 ?
[08:25] <davmor2> ogra_: davmor3 is my evil twin brother you don't want his opinion ;)
[08:52] <popey> xcihelp: (possibly fginther as he last touched it) calc reboot is doing two jenkins jobs per merge.  https://code.launchpad.net/~nikwen/ubuntu-calculator-app/reboot-white-splash-screen/+merge/255912
[08:52] <popey> bah
[08:52] <popey> cihelp: (possibly fginther as he last touched it) calc reboot is doing two jenkins jobs per merge.  https://code.launchpad.net/~nikwen/ubuntu-calculator-app/reboot-white-splash-screen/+merge/255912
[09:45] <dbarth_> trainguards: ping? do you still need an oxide build for ota-3 ?
[09:50] <Mirv> dbarth_: my understanding was that it landed in http://people.canonical.com/~ogra/touch-image-stats/rtm/270.changes
[09:50] <Mirv> and is being tested now
[09:51] <ogra_> was 1.6.2 the one we were waiting for ?
[09:51]  * ogra_ isnt up to date with these version numbers
[09:52] <Mirv> ogra_: 1.6.3, you mean?
[09:52] <Mirv> liboxideqtcore0:armhf from 1.6.2-0ubuntu0.14.10.1~ppa1 to 1.6.3-0ubuntu0.14.10.1~ppa1
[09:52] <ogra_> err, yes ;)
[09:56] <dbarth_> 1.6.3 yes, with the viewport zoom fix
[09:56] <dbarth_> Mirv: ok, thanks; just checking in case there was something stuck
[09:58]  * ogra_ has recieved the update on sunday morning ... i dont see any ill behavior here 
[10:04] <dbarth_> ogra_: the issue was about https://bugs.launchpad.net/oxide/+bug/1442458
[10:04] <ogra_> yeah, i know :)
[10:04] <ogra_> i tried a few desktop sites, they all worked fine, no carshes
[10:04] <ogra_> (i didnt try the welcome wizard, thats up to QA)
[11:23] <ogra_> fginther, plars, can either of you explain to me why desktop kernel adt runs happen on krillin devices ?
[11:24]  * ogra_ is specifically looking at http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/AutoPkgTest/job/vivid-adt-linux/lastBuild/? on the private jenkins instance ... it says it runs on krillin-08 ?
[11:26] <ogra_> (and why the heck does a one line change in initramfs-tools result in a kernel build from source as test ... )
[12:58] <pmcgowan> morning
[13:03] <seb128> hey pmcgowan
[13:04] <pmcgowan> seb128, hey
[13:04] <pmcgowan> no sil or jibel it seems
[13:05] <ogra_> nope, both off
[13:05] <pmcgowan> who is doing regression testing?
[13:05] <ogra_> pmcgowan, 270 has all the changes
[13:05] <pmcgowan> indeed
[13:05] <ogra_> not sure who in QA does the tests
[13:05] <pmcgowan> rvr, maybe?
[13:05] <ogra_> davmor2, ^^^ ?
[13:06] <pmcgowan> 270 works for me this weekend
[13:06] <ogra_> same here
[13:06] <ogra_> no issues with desktop sites or zooming
[13:06] <popey> ship it!
[13:06] <ogra_> yeah, who needs QA signoff
[13:08] <davmor2> pmcgowan: QA are, jibel is at the sprint not sure yet who will post the results. we are currently re-running anything that is reliant on the browser so far so good, so be back to you shortly
[13:08] <pmcgowan> davmor2, very good
[13:16] <balloons> cihelp, can you check the jenkins jobs for calculator app? It seems both the normal job and the reboot job are running on mp's
[13:16] <balloons> see https://code.launchpad.net/~nikwen/ubuntu-calculator-app/reboot-white-splash-screen/+merge/255912
[13:18] <ted> rsalveti, Thanks for reviewing the i-sound branch and throwing it into your silo!
[13:26] <Mirv> dbarth_: ^
[13:31] <Mirv> ogra_: could you ack compiz + unity packaging changes? switch to python3 in migration scripts https://ci-train.ubuntu.com/job/ubuntu-landing-014-2-publish/
[13:31] <bregma> it's just a little ack
[13:32] <ogra_> Mirv, ack ...
[13:33] <Mirv> ack!
[13:49] <dbarth_> Mirv: approved
[13:50] <dbarth_> Mirv: could you also help me reconfig silo 22 (i swapped a branch but there's no reconfig button in the spreadsheet that i can find)
[13:54] <fginther> popey, balloons, I've disabled the calculator-app-reboot jobs
[13:55] <popey> thanks fginther
[13:55] <fginther> popey, sorry for the delay, we're sprinting this week
[13:56] <balloons> fginther, :-)
[13:56] <popey> no worries
[13:59] <fginther> ogra_, desktop kernel adt runs? are you referring to where jenkins is running jobs?
[14:00] <ogra_> fginther, i'm referring to proposed migration ... an upload of initramfs-tools causes a complete source to binary build of the kernel source ... which is totaly pointless and wastes several hours (turnaround time for initramfs-tools used to be a few minutes) ... it also runs completely pointless boot tests on phones now
[14:01] <ogra_> fginther, we need a white/blacklist or some such to not bluntly run such tests on totally unrealted packages
[14:15] <Mirv> dbarth_: note the new reconfig option in the landing tools menu, can you try it?
[14:16] <fginther> ogra_, ok, I see now what you are referring too... initramfs-tools has a reverse dependency on the kernel (which must complete its autopkg test in order to pass). So, I understand your comment now.
[14:16] <ogra_> fginther, riht, i would like us to have a white/blacklist for such special cases where we can permanently override pointless tests
[14:27] <rsalveti> ted: thanks for the fix :-)
[14:50] <sil2100> jibel_: http://people.canonical.com/~lzemczak/landing-team/ota/ota-3.commitlog <- here's the commitlog, but as I was afraid, we're missing many landing bindings because of the problems with the spreadsheet
[14:52] <sil2100> Mirv: hey! Any problems with landings in teh morning?
[15:02] <jgdx> trainguards, could you please reconfigure silo 6? Thank you.
[15:02] <sil2100> jgdx: on it
[15:02] <jgdx> sil2100, thank you
[15:04] <sil2100> jgdx: done
[15:04] <jgdx> sil2100, rog
[15:08] <jgdx> thank you queuebot, you rock
[15:08] <sil2100> ;)
[15:11] <Mirv> sil2100: nothing special
[15:12] <Mirv> sil2100: good flights? :)
[15:12] <davmor2> sil2100: has become cancel crazed someone slap him back to his senses
[15:13] <sil2100> Mirv: longish, but I survived (no murderous pilots)
[15:14] <Mirv> survival is the most important thing..
[15:15] <sil2100> davmor2: ha, robru is really happy with that change!
[16:06] <om26er> pete-woods, Hi!
[16:25] <om26er> pete-woods, How can I verify fix in bug 1434379 ?
[16:32] <nerochiaro> bfiller_meeting: ok, i will wrap up this one in a way that anyone can pick it up, then discuss with olivier and get on these tomorrow morning
[16:32] <rsalveti> om26er: http://paste.ubuntu.com/10816903/
[16:32] <rsalveti> om26er: this was how it got validated for RTM
[16:35] <om26er> rsalveti, I was planning to ask you incase I didn't get response from Pete :)
[16:52] <om26er> ted, Hi! is bug 1437355 strictly desktop-specific ?
[16:53] <robru> Saviq: https://code.launchpad.net/~nick-dedekind/ubuntu-settings-components/1390136.laggy-backends/+merge/252754 need this top approved in order to publish
[16:55] <Mirv> indeed
[16:57] <ted> om26er, No, it's device only. It is in the desktop hook.
[16:57] <ted> om26er, Which is the hook used to process desktop files.
[16:58] <om26er> ted, heh, ok. The comment in the spreadsheet made it sound like it was desktop specific.
[17:02] <Saviq> robru, sorries, ACKed
[17:02] <robru> Saviq: thanks
[17:05] <robru> Saviq: https://ci-train.ubuntu.com/job/ubuntu-landing-025-2-publish/lastSuccessfulBuild/artifact/unity8_packaging_changes.diff/*view*/ so this looks really wrong, is this upload intended to revert version ...320?
[17:46] <om26er> ted, anything else to look for except for the TestPlan ?
[18:34] <rvr> alex-abreu: Besides manual tests, anything special to check for silo 17? (Remove webbkit dependencies)
[18:35] <alex-abreu> rvr, besides webapps & webbrowser tests, nothing really
[18:36] <rvr> alex-abreu: Oookis. Approving it.
[18:52] <robru> dbarth__: alex-abreu: justinmcp: need these MP's top-approved: https://ci-train.ubuntu.com/job/ubuntu-landing-017-2-publish/69/console
[18:53] <alex-abreu> robru, approved them
[18:53] <robru> alex-abreu: thanks
[19:03] <dbarth__> robru: ah, alex-abreu beat me to it :)
[19:06] <robru> dbarth__: thanks for checking!
[19:06] <robru> ted: hey it seems we have 5 free silos now, did you want that vivid+1 one now?
[19:16] <Saviq> robru, this looks wrong indeed, but none of the unity8 MPs touch the changelog...
[19:16] <Saviq> robru, so it must've been the train that messed up the changelog??
[19:24] <robru> Saviq: yikes, i'm not sure how...
[19:26] <robru> Saviq: the only thing I can suggest is to rebuild, but I just checked the timestamps, and the most recent build is newer than when the last release merged to trunk, so I don't know how this situation could have arisen. this kind of thing should only happen if you build a new silo before the previous silo finishes merging.
[19:32] <robru> Saviq: don't rebuild yet, I'll poke at some stuff and see what happens...
[19:33] <Saviq> robru, I just looked at the full diff and at least the contents are correct
[19:33] <popey> 32
[19:34] <popey> bah
[19:34] <Saviq> robru, so at worst I'd rather we publish that and fix changelog manually
[19:35] <robru> Saviq: oh, ok... hmmmm
[19:36] <robru> Saviq: ok, will publish then.
[19:37] <Saviq> tx
[19:37] <robru> Saviq: i'll prep a branch with a fixed changelog that we can merge once that lands
[19:57] <sil2100> jibel: wow, devel image promotion takes like 15 minutes per one image or even more
[22:18] <sil2100> popey: hey!
[22:18] <popey> hello sil2100
[22:18] <sil2100> popey: in case you're still around...
[22:18] <sil2100> popey: we have a problem with calculator!
[22:18] <sil2100> ;)
[22:18] <popey> what?
[22:18] <sil2100> popey: sooo, basically the reboot of a reboot broke all smoketesting, since it has no tests
[22:18] <popey> I specifically raised this before it landed with fginther
[22:19] <popey> because I expected this. He said he'd fixed it.
[22:19] <sil2100> popey: and since smoketesting infrastructure assumes and expects each of the apps to have tests, it's b0rken
[22:19] <sil2100> hm, I still see 4 images without tests along with the newest one
[22:20] <sil2100> popey: anyway, I guess the simplest and best fix would be to add at least one quick almost-dummy test
[22:20] <sil2100> I think we did the same for terminal once
[22:20] <sil2100> popey: could you maybe contact the app developers about that?
[22:21] <popey> le sigh
[22:21] <sil2100> Oh
[22:21] <sil2100> popey: actually!
[22:21] <popey> frustrating given I pre-empted this
[22:21] <sil2100> popey: wait wait, heh... actually jibel said there are tests but they're in a non-standard directory
[22:24] <sil2100> popey: so, hmmm...
[22:25] <popey> bfiller: happy belated birthday
[22:26] <sil2100> popey: so, anyway, for the smoketesting to work we would need the tests/ directory be in the main source directory
[22:27] <sil2100> popey: since otherwise phablet-click-test-setup won't be able to find it
[22:27] <sil2100> popey: it's not smart enough to look for the tests in random directories ;p
[22:27] <popey> sil2100: if someone wants to prepare a merge, I'll take a look and approve now.
[22:29] <sil2100> I'll try looking into that later maybe, would be best for a real app developer to do that since he has better knowledge of why actually all of that is in the /app directory
[22:29] <sil2100> popey: could you forward that to someone if I don't prepare a merge beforehand?
[22:31] <popey> sil2100: would be more helpful if the person who found this issue filed a bug against calculator.
[22:31] <popey> and then we can prioritise it accordingly
[22:35] <sil2100> popey: will do that now
[22:38] <popey> thanks
[22:45] <sil2100> popey: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1443680
[22:46] <sil2100> popey: as said, tomorrow I might find time to quickly patch-up an MR
[22:46] <popey> uhhhh
[22:46] <popey> calendar?
[22:46] <popey> you said calculator?
[22:46] <sil2100> AaaaaAAh
[22:46] <sil2100> Crraaap
[22:46] <sil2100> Sorry, calculator it was supposed to be
[22:46] <sil2100> Bah
[22:46]  * sil2100 is stupid
[22:47] <popey> heh
[22:47] <popey> thanks for filing
[22:47] <sil2100> popey: https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1443680
[22:48]  * popey thinks that phablet-click-test-setup shouldn't be this fragile
[22:48]  * popey further thinks the entire infra breaking because _one_ app fails is madness cubed.
[22:48] <popey> but we've had this conversation before, the last time this happened.
[22:48] <popey> ..and we'll have it again, the next time.
[22:48] <popey> :(
[22:48] <sil2100> popey: well, I wouldn't say phablet-click-test-setup is too fragile here, I think that the smoketesting infra shouldn't be so stupid
[22:49] <sil2100> So the smoketesting part is the part that's wrong here
[22:49] <popey> Ya.
[22:49] <popey> One we can laugh about over a beer in a few years.
[22:49] <sil2100> But that's a CI project, and they're overloaded with work
[22:49] <sil2100> :|
[22:51] <sil2100> So best way to fix it is to fix it on our side
[23:18] <sil2100> o/