[05:52] <Mirv> Saviq: yes, dbarth promised to keep on staring at the xenial part
[05:53] <Mirv> and I did too
[05:53] <Mirv> now it seems finally done, the queue was just again so freakingly big
[08:34] <dbarth_> cjwatson: sorry; here is the answer from yesterday: https://launchpad.net/~oxide-builds
[08:38] <dbarth_> cjwatson: Chris had left a question on https://answers.launchpad.net/launchpad/+question/287462 to get the ugprade
[08:40] <dbarth_> cjwatson: next week would be fine if you expect storage to arrive soon
[08:41] <abeato> sil2100, morning
[08:42] <abeato> sil2100, I need a new rc for frieza, using device tarball http://people.canonical.com/~abeato/avila/ubuntu/device_frieza-20160309.0.tar.xz , mind triggering that?
[08:58] <Mirv> seb128: if you had the possibility, the libubuntutoolkit5/-dev at binNEW review would be still waiting (some bugs fixed in the same silo meanwhile) https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-050/+sourcepub/6183236/+listing-archive-extra
[08:59] <sil2100> abeato: sure
[08:59] <abeato> thanks
[08:59] <seb128> Mirv, oh right, going to try to get to that this morning
[09:00] <Mirv> ok, thanks
[09:20] <sil2100> abeato: done :)
[09:20] <abeato> sil2100, thanks :)
[09:38] <dbarth_> sil2100: hey, back on the issue i had yesterday about the need to rebuild a silo or not
[09:38] <dbarth_> sil2100: https://requests.ci-train.ubuntu.com/#/ticket/893
[09:39] <dbarth_> it's been tested and so on; but some commits short-circuited us
[09:44] <sil2100> hmm
[09:49] <dbarth_> sil2100: yeah...
[10:05] <sil2100> dbarth_: problematic, the directly-uploaded change for indicator-datetime looks like something we shouldn't overwrite
[10:05] <sil2100> dbarth_: not sure what the train means by calendar-app having new commits - did anyone push to trunk in the meantime?
[10:08] <anpok_> hm I am runnning the webbrowser autopilot tests as part of our mir release plan.. is there a known issue in rc-proposed? I get 64 failures with the plain ubuntu-touch/rc-proposed/ubuntu image
[10:08] <robru> sil2100: yes there are new commits on trunk, if you click through to the Jenkins log it shows that
[10:13] <dbarth_> so that's a rebuild, and a re-qa :/ maybe fast tracked if possible
[10:13] <dbarth_> i'll trigger the new rebuild now
[10:13] <robru> dbarth_: well, theoretically you could release the silo as is
[10:13] <sil2100> dbarth_: yeah, for indicator-datetime I would also recomment re-including stgraber's change and adding it to one of the merges
[10:13] <sil2100> dbarth_: https://launchpadlibrarian.net/247161942/indicator-datetime_15.10+16.04.20160129-0ubuntu1_15.10+16.04.20160129-0ubuntu2.diff.gz
[10:14] <robru> dbarth_: the trunk commit would be included in the next release instead of this one
[10:14] <robru> sil2100: dbarth_ no it doesn't work to add a distro upload to one of the MPs, you need to commit it direct to trunk
[10:14] <sil2100> For calendar yeah, I suppose
[10:15] <sil2100> robru: we could force-publish it then, overwriting it but the change would still be there
[10:15] <dbarth_> would it?
[10:15] <sil2100> dbarth_: it would if you would include it in one of the MPs
[10:16] <sil2100> dbarth_: or you can do it as robru said, so direct-push to trunk and then rebuild indicator-datetime
[10:16] <sil2100> Any solution is fine for me, we don't really care that much about package history
[10:16] <robru> dbarth_: sorry there's two things, I'm talking about calendar, the trunk commit will be built in the next build if you publish the current thing without it. Indicator of different, publishing will clobber the distro upload
[10:16] <dbarth_> right
[10:16] <dbarth_> so they need to be managed differently
[10:17] <dbarth_> i think we can deal more simply with the calendar part
[10:17] <dbarth_> the indicator-datetime part is where i need to take care
[10:18] <dbarth_> to double check; i need to modify one of the MPs to add the change from stgraber to it, and rebuild the silo with that updated MP, correct?
[10:18] <dbarth_> to make sure the commit won't conflict, on xenial specifically
[10:20] <dbarth_> bbiab, sorry
[10:27] <robru> dbarth-afk: yeah i guess that would work but it didn't really make sense. Don't sully a good mp with an unrelated change, just commit direct to trunk, as the manual distro upload is conceptually similar to a direct trunk commit.
[10:28] <robru> Anyways, gnight ;-)
[11:26] <davmor2> Saviq: is you team responsible for the welcome wizard?
[11:36] <dbarth> rvr: i will need some record of whether calendar-app and indicator-datetime are good to land from a qa perspective; re: silo 003
[11:37] <dbarth> right now the calendar-app changes have been merged already (xenial and vivid as trunk doesn't make a difference afaict)
[11:38] <rvr> dbarth: Silo 3, let me see
[11:38] <dbarth> and indicator-datetime had been qa'ed and proved to work afaict as well, on vivid at least, where the packages and branches seem good
[11:39] <dbarth> so i would request a qa waiver for xenial, to then ask charles to commit the branches to indicator-datetime trunk (xenial)
[11:40] <rvr> dbarth: Well, it seems it is still not ready "Destination version 15.10+16.04.20160129-0ubuntu2 is missing from changelog (indicator-datetime/xenial). Needs rebuild due to new commits (calendar-app/xenial)". But I don't know how bileto does those checks and how to fix them. You need to talk to sil2100 or robru.
[11:40] <dbarth> rvr: i was having that discussion with them an hour ago
[11:40] <dbarth> from their pov i could land, albeit with some contorsions
[11:41] <dbarth> but before i go down that path, i also need a record from you about the silo being functionally good
[11:42] <rvr> dbarth: Ah, if they are ok, then I will unblock the card and move it to the ready for QA lane.
[11:43] <rvr> Done
[11:43] <dbarth> rvr: ok cool; but you hadn't tested it already? or popey?
[11:44] <rvr> dbarth: I haven't
[11:44] <dbarth> the calendar part got merged (and released on the store)
[11:44] <dbarth> rvr: hmm, ok; then i'll let you double check on vivid that the i-datetime part works as expected with the new calendar-app click
[11:45] <dbarth> ping me back when i can annoy everyone again about that landing
[11:46] <rvr> dbarth: Ack
[11:49] <davmor2> Saviq: is you team responsible for the welcome wizard? first page of the welcome wizard is in blue text
[11:54] <dbarth> thanks
[12:20] <Saviq> davmor2, right, yes, please add a screenshot to bug #1554616
[12:26] <davmor2> Saviq: done thanks
[13:22] <rvr> jgdx: Silo 5 approved, happy to see all gmail notifications :)
[13:22] <jgdx> rvr, thank you and I'm glad to hear it.
[13:28] <Elleo> trainguards: could someone trigger a rebuild of silo 69 on vivid arm64 please?
[13:42] <sil2100> Elleo: on it
[13:43] <sil2100> Elleo: done
[13:43] <Elleo> sil2100: thanks :)
[13:49] <Mirv> robru: hi. there's something specifically wrong with https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-045/excuses.html in that it hasn't been updated since the morning (2016.03.09 04:08:51 +0000)
[14:19] <sil2100> cjwatson: hey! Do you think there would be a possibility for me to get some kind of write access to the public_html/click_packages ubuntu-archive directory on snakefruit?
[14:19] <sil2100> cjwatson: to that dir exclusively
[14:22] <sil2100> anpok_, morphis: hey! How's the silo 21 testing going? I see the emulator got tested, right?
[14:27] <morphis> sil2100: yes, jhodapp tested mako yesterday
[14:27] <sil2100> Looking good so far?
[14:27] <morphis> sil2100: yes
[14:27] <sil2100> We can't wait for the emulator unblock ;)
[14:27] <morphis> sil2100: yeah, I saw your mail :-)
[14:28] <ogra_> stop fixing the emulator, sell moar phones !
[14:28] <morphis> sil2100: btw. devel-proposed still doesn't boot, right?
[14:28] <jhodapp> morphis, sil2100 working on testing flo now
[14:28] <morphis> jhodapp: good
[14:28] <sil2100> morphis: yeah, still down, ondra is assigned to it
[14:28] <sil2100> jhodapp: excellent
[14:28] <jhodapp> sil2100, should the xenail dev image on mako be booting atm? For me it never gets past the Google logo
[14:28] <morphis> jhodapp: so lets skip xenial then :-)
[14:29] <sil2100> jhodapp: sadly devel-proposed is busted right now, you'd have to test on devel
[14:29] <jhodapp> morphis, yeah not much I can do there anyway
[14:29] <sil2100> jhodapp: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150
[14:29] <sil2100> jhodapp: but devel is pretty recent, it's a few weeks old but at least boots ;)
[14:29] <jhodapp> sil2100, ok
[14:29] <sil2100> (in case it has all the packages you need of course)
[14:29] <jhodapp> sil2100, worth testing these tarballs on?
[14:30] <sil2100> I suppose would be nice to at least do a quick one
[14:30] <sil2100> Just to make sure we won't make something unbootable or such after devel-proposed is unblocked
[14:30] <jhodapp> sil2100, sure, I'll test it after vivid then
[14:31] <sil2100> Thanks :)
[14:48] <cjwatson> sil2100: that sounds technically challenging to arrange, but also unnecessary; that directory is maintained by a cron job
[14:48] <cjwatson> sil2100: the cron job in question lives in lp:~ubuntu-cdimage/click-sync/trunk
[14:49] <sil2100> cjwatson: hmmmm... ok, so I have an idea how to workaround this without requiring this permission change, in case that is not viable
[14:50] <sil2100> cjwatson: since we'll be doing some workarounds for locking down certain clicks, but now that I think of it it doesn't need to necessarily be in the same directory
[14:50] <sil2100> cjwatson: anyway, thanks for pointing to the cronjob :)
[14:50] <sil2100> This I didn't know and was actually wondering where that's stored
[14:50] <cjwatson> dbarth: I've left a comment on https://answers.launchpad.net/launchpad/+question/287462 - it will indeed need to wait until next week.
[14:51] <ogra_> sil2100, you committed to it 33 min ago :P
[14:51] <sil2100> Yeah, now I noticed, ok, so I'm actually looking for the crontab with cronjobs ;p
[14:51] <sil2100> Not the actual script being run
[14:52] <sil2100> cjwatson: do you know if the cron-line for executing click-sync is available somewhere?
[14:53] <sil2100> i.e. would it be possible for me to change the click-sync arguments in the crontab by myself somehow or will I have to poke someone from ubuntu-archive?
[14:54] <cjwatson> 11,41 * * * *           bzr up -q ~/click-sync && ~/click-sync/click-sync.py --credentials-file ~/.config/click-toolbelt/credentials.json https://jenkins.qa.ubuntu.com ~/public_html/click_packages
[14:54] <cjwatson> You won't be able to change those by yourself
[14:57] <sil2100> Thanks
[15:08] <Elleo> sil2100: heya, that arm64 rebuild on vivid for silo 69 doesn't seem to have rebuilt, it's still listed as just having failed 21 hours ago?
[15:08] <sil2100> huh, maybe I got a timeout
[15:08] <sil2100> Retrying...
[15:08] <Elleo> thanks
[15:14] <dbarth> cjwatson: ack
[16:19] <seb128> Mirv, those binNEW looks fine, feel free to publish it
[16:20] <jhodapp> sil2100, is it a known bug that audio recording isn't working at all on the latest rc-proposed images for mako and flo (and perhaps other devices)?
[16:31] <sil2100> jhodapp: hm, didn't hear about it so far
[16:31] <sil2100> jibel, davmor2: ^ ?
[16:31] <jhodapp> sil2100, I've just run into it was mako and flo last night and today
[16:31] <jhodapp> image 382 for both
[16:32] <davmor2> sil2100, jhodapp: hmm should be unless the pulseaudio had some config left over in the silo, let me try hear
[16:33] <davmor2> jhodapp: I get audio recording on latest on arale
[16:33] <davmor2> sil2100: ^
[16:34] <davmor2> let me flash mako
[16:36] <jhodapp> davmor2, it may be mako flo specific as they're pretty much the same thing
[16:36] <davmor2> jhodapp: I'll let you know shortly
[16:36] <jhodapp> ok
[16:37] <rvr> alex-abreu: Silo 16 approved
[16:37] <alex-abreu> rvr, awesome thx !
[16:48] <davmor2> jhodapp: confirmed I blame morphis  ;)
[16:49] <jhodapp> :)
[16:49] <jhodapp> davmor2, sil2100 same is true for the xenial image on both
[16:50] <davmor2> jhodapp: you think xenial boots wow when did that get fixed
[16:50] <jhodapp> davmor2, hehe, the devel, not the proposed
[16:51] <davmor2> jhodapp: devel is ancient
[16:51] <jhodapp> yeah, but seems to suffer the same recording issue
[16:51] <davmor2> jhodapp: so that could be cpp issue a xenial issue or something else altogether
[16:52] <jhodapp> yeah
[16:52] <davmor2> or a libhybris I guess
[16:53] <davmor2> morphis: is it likely that mako and flo might need a libhybris update maybe?
[17:12] <Saviq> davmor2, do you plan to have a verdict on UITK today?
[17:13] <davmor2> Saviq: depends do you promise that you will fix the welcome wizard asap, hum hum hum ?  ;)
[17:14] <Saviq> davmor2, I will replace it https://requests.ci-train.ubuntu.com/#/ticket/255
[17:14] <davmor2> Saviq: should be any second I think I've found the only issues I'm going to find and I think they are all application bugs now rather than uitk so will pass it shortly
[17:14] <Saviq> davmor2, ack, thanks!
[17:26] <davmor2> Saviq, zsombi: any second
[17:28] <zsombi> davmor2: one :)
[17:28] <Saviq> w00t w00t!
[17:29]  * Saviq publishes
[17:29] <Saviq> will probably faile due to missing privileges
[17:29] <Saviq> -e
[17:30] <davmor2> yay
[17:30] <davmor2> Saviq: it's nice when the bot says you suck right ;)
[17:30] <Saviq> mterry, can you please have a look at packaging ↑
[17:30] <mterry> Saviq, sure
[17:30] <Saviq> yeah, could be a bit more delicate
[17:31] <Saviq> like I am
[17:36] <Saviq> oops, we'll kinda skip the previous unity8 migration to xenial... oh well
[17:39] <Saviq> mterry, thankies
[17:55] <bzoltan_> Saviq:  exciting times :)
[17:59] <Saviq> bzoltan_, and it only took two weeks ;P
[18:00] <Saviq> bzoltan_, FWIW, unity8's autopilot and QML tests are meant to pass, sometimes not on first try (we're trying to eradicate flaky tests), but overall they need to pass - we'd have found the crashing wizard earlier if the results were looked at
[18:01] <bzoltan_> Saviq: No stress anymore :)
[18:01] <pmcgowan> bzoltan_, wow quite a silo that 50
[18:01] <bzoltan_> pmcgowan:  tell me about it :) took two months to get it in
[18:02] <bzoltan_> pmcgowan: comsulted with cardiologist few times during the time
[18:02] <pmcgowan> landing drugs
[18:13] <bzoltan_> pmcgowan: landing 9 OTA bugfixes feels like being on drugs...I guess :)
[18:34] <davmor2> jhodapp: did you file a bug for the issue with recording?
[18:35] <jhodapp> davmor2, no
[19:25] <boiko> robru: I can't remember, if I remove one component from a silo, do I need to assign it again?
[19:27] <morphis> davmor2: not sure, but which audio recording is not working? as it could be the changed pulseaudio too :-)
[19:29] <morphis> davmor2, jhodapp: can one of you file a bug for that?
[19:29] <morphis> against pulseaudio would be a good start :-)
[19:30] <robru> boiko: no but you need me to delete it from the ppa
[19:31] <boiko> robru: could you please remove history-service from silo 40 then?
[19:32] <jhodapp> morphis, sure
[19:32] <robru> boiko: yeah gimme a minute, just need coffee
[19:32] <boiko> robru: sure, no rush, and coffee is always a good idea :)
[19:36] <jhodapp> morphis, davmor2: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1555307
[19:42] <davmor2> jhodapp: thanks dude
[19:42] <jhodapp> np
[19:43] <robru> boiko: ok done
[19:43] <boiko> robru: thanks!
[19:43] <robru> boiko: you're welcome
[19:43] <robru> (it'll notice in a minute)
[19:45] <robru> boiko: ^^ that did nothing btw
[19:47] <boiko> robru: yeah, I was not sure if my last commits to messaging-app were built (as the silo was still showing as failed because of history)
[19:47] <boiko> robru: I triggered a rebuild to be sure :)
[19:48] <robru> boiko: if there were new commits it would say "needs rebuild due to new commits"
[19:48] <boiko> robru: yep ok, I'll wait next time :D
[19:50] <morphis> jhodapp: thanks!
[19:51] <jhodapp> np
[19:51] <jhodapp> morphis, btw, libhybris testing is complete
[19:51] <morphis> jhodapp: oh great you did that too!
[19:51] <jhodapp> yeah looks good to me
[19:51] <morphis> jhodapp: you're rocking, man!
[19:52] <jhodapp> thanks :)
[19:52] <morphis> jhodapp: then lets switch both to approved
[19:52] <jhodapp> morphis, do you have an MR for them?
[19:52] <morphis> jhodapp: no
[19:52] <morphis> everything already merged
[19:52] <jhodapp> right ok, you mean in the silo
[19:52] <jhodapp> set to approved
[19:52] <morphis> yeah
[19:53] <jhodapp> sure will do
[19:53] <morphis> jhodapp: https://git.launchpad.net/~libhybris-maintainers/libhybris/+git/libhybris/log/ is what it looks like
[19:53] <morphis> jhodapp: approved both requests already :-)
[19:53] <jhodapp> nice thanks
[19:53] <morphis> davmor2: more work for you :-)
[19:53] <jhodapp> morphis, I like the ubuntu screen for recovery
[19:54] <davmor2> morphis: no no I refuse to believe that :p
[19:54] <morphis> davmor2: I think there are new cards on your board now :-)
[22:41] <Saviq> robru, hey, think we could force merge https://requests.ci-train.ubuntu.com/#/ticket/905 ? It's the same situation as yesterday - armhf backed up and everything else passed fine (or at least didn't regress) - same as happened in the silo before
[22:43] <robru> Saviq: OK
[22:44] <Saviq> thanks
[22:45] <robru> Saviq: yw