[02:05] <imgbot> [03:30] <imgbot> [03:30] <imgbot> [07:25] <Mirv> btw all testing about #146 boot problems welcome, since my device is stuck running autopilot tests on #145
[07:56] <bzoltan_> Mirv:  I could use a vivid silo for the UITK
[08:12] <Mirv> bzoltan_: 012. conflicts with Saviq's/mzanetti's 015 but I guess the DPR is not yet landing
[08:15] <ogra_> oh, since i got two Qt experts here ....
[08:16] <ogra_> Mirv, bzoltan_, why doesnt this work: http://paste.ubuntu.com/10667273/
[08:16] <ogra_> looks like a bug to me
[08:16] <ogra_> (note that ricmm ponted me to ted, who pointed me to the sdk :) )
[08:17] <Mirv> "I just package it" :D
[08:17] <Mirv> ogra_: try asking on #ubuntu-app-devel
[08:17] <ogra_> hardcoding the application name works fine
[08:17] <Mirv> where also the rest of the SDK team is on besides zoltan
[08:19] <Mirv> maybe it is a bug, but where
[08:25] <sil2100> Morning
[08:25] <sil2100> I seem to have a power outage at home
[08:26] <sil2100> The power company mentioned it might take a few hours
[08:26] <sil2100> Im on 3G right now
[08:33] <Mirv> sil2100: :(
[08:34] <Mirv> hangouts over 3G is doable, but hangouts might eat all the battery power..
[08:34] <Mirv> and morning
[08:39] <sil2100> And my data packet!
[08:39] <sil2100> Since I dont have unlimited internet, geh
[08:40] <sil2100> Mirv: for now please take care of teh train
[08:41] <sil2100> Ill jump out and try finding a place for hangouts, but if not, I wont be able to make it
[08:41] <sil2100> Leaving my irc session on this host though
[08:42] <Mirv> sil2100: sure, teh train will be in good hands
[08:48] <ogra_> imgbot, status 146 vivid
[08:48] <imgbot> Status: succeeded, Started: 2015-03-24 02:02:04 UTC, Finished: 2015-03-24 02:57:56 UTC
[08:48] <imgbot> Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/+build/23282
[08:48] <imgbot> Changelog: http://people.canonical.com/~ogra/touch-image-stats/146.changes
[08:49] <Mirv> ...whether it boots or not remains to be verified
[08:49] <Mirv> if anyone can flash, please do. my device is stuck in AP duties.
[08:50] <ogra_> well, it is the only one that built tonight ... all other flavours failed
[08:50] <ogra_> i needed the build log :)
[09:30] <sil2100> Trying to log into the ho
[09:32] <sil2100> Can anyone give me the hangout link?
[09:32] <ogra_> https://plus.google.com/hangouts/_/canonical.com/landing-meeting
[09:32] <sil2100> Thanks
[09:46] <Mirv> davmor2: as soon as the new XPS 13 is available :)
[09:46] <Mirv> ie as soon as the remaining bugs are fixed... which they should be now, about
[09:46] <Mirv> so hopefully April
[09:54] <sil2100> Damn, not sure what they're blocking on this wifi, but damn
[10:17] <bzoltan_> Mirv:  thanks for your kind assistance, I have just added the gles branch to the landing line. I wonder if my "reconfigure" worked ... if not, would you mind to reconf the silo12?
[10:23] <mzanetti> trainguards: please reconfig silo 15 for me (I've added ubuntu-settings-components)
[10:28] <bzoltan_> trainguards: ^^ same for silo 12 please too
[10:40] <Mirv> eating, but booting up my mini laptop...
[10:41] <Mirv> just a moment
[10:47] <Mirv> bzoltan_: mzanetti: both done, in theory. "success" but "error". please ping sil2100 with https://ci-train.ubuntu.com/job/prepare-silo/4441/console + https://ci-train.ubuntu.com/job/prepare-silo/4442/console if it doesn't wor for you
[10:47]  * Mirv resumes eating
[10:48] <sil2100> huh
[10:48] <sil2100> Success with error, love that
[11:16] <Mirv> sil2100: I'm getting that "ERROR Silo config file changed out from under us!" on all reconfigs
[11:17] <Mirv> and to me it'd look like that indeed also bzoltan_'s and mzanetti's silos were not really reconfigured because of that
[11:19] <mzanetti> Mirv, yap, not actually reconfigured
[11:23] <sil2100> Looking into that now
[11:23] <sil2100> Home still has no power though...
[11:31] <sil2100> hmm
[11:37] <ogra_> Mirv, just FYI, latest image boots fine for me on arale
[11:37] <ogra_> it triggered an apparmor cache rebuild though ... took quite a while to come up
[11:40] <Mirv> great
[11:40] <sil2100> Mirv: hm, there might be indeed a train issue right now
[11:41] <sil2100> Without power and inrernet debugging is slow, but I'm getting there
[11:42] <sil2100> Mirv: can you retry reconfiguring silo 12 for me?
[11:43] <Mirv> sil2100: ok. with Atom processor it's slow for me too, but no problem :)
[11:44] <Mirv> (I stuck at the lunch place since things to do kept coming)
[11:44] <sil2100> No worries, thanks! ;)
[11:44] <Mirv> 1.83GHz of sheer processing power
[11:44] <Mirv> ...equal to PIII 900MHz or so
[11:45] <davmor2> Mirv: just but a new laptop already ;)
[11:46] <Mirv> davmor2: I _can't_ buy last year's model when the new one is almost within my reach if I hold my breathe :)
[11:46] <sil2100> jibel, davmor2: were you able to double confirm the issues with first boot unity8 greeter missing?
[11:46] <Mirv> sil2100: train is still being coward https://ci-train.ubuntu.com/job/prepare-silo/4445/console
[11:46] <davmor2> sil2100: no
[11:47] <davmor2> Mirv: don't do that you'll die before it's really you need air
[11:47] <davmor2> s/really/ready
[11:48] <sil2100> Mirv: hm hm, looking deeper, but looks like the new train code has some race and something somewhere touches the config inbetween the start of the job and the final check
[11:48] <Mirv> davmor2: the shipping date is sooo close I just might be able to do it!
[11:50] <Mirv> or I could settle for Precision M3800 Developer Edition shipping already now but it's a bit overkill and not so suitable for traveling (even though the 1.8kg is impressive for what it delivers)
[11:51] <Mirv> sil2100: yeah, I wonder if no-one reconfigured anything yesterday and it wasn't found therefore earlier
[11:51] <Mirv> sil2100: are the current steps to deploy an older version documented somewhere?
[11:52] <Mirv> with robert away this week we might need to consider reverting if there are problems
[11:53] <sil2100> hm, I think we had some documentation for that
[11:53] <sil2100> I just hope publishing works
[11:54] <sil2100> Mirv: want me to handle that ^? ;)
[11:54] <Mirv> it does
[11:54] <Mirv> sil2100: I'm already pressing the Publish button.. unless you want it? :) but I published two rtm silos earlier today just fine
[11:54] <sil2100> Publish publish ;)
[11:55] <sil2100> Thanks
[11:55] <Mirv> looks like vivid publishing also works
[11:55]  * sil2100 saves his precious packets
[11:55] <Mirv> as does building and assigning silos
[11:55] <Mirv> only reconfiguring is a problem
[11:56] <Mirv> so... we can reconfigure by assigning a new silo and deleting the old one ;)
[11:56]  * Mirv walks back to a faster machine
[11:58] <sil2100> hah, nce workaround ;) Problem is that then the silo state is lost and everything needs to be rebuolt
[11:58] <sil2100> I'll try reverting the train once I have my power back
[12:06] <sil2100> It's 13 here already, I should have my power back on but it's still not
[12:19] <sil2100> Let me publish silo 13
[12:19] <Mirv> sil2100: too late :)
[12:20] <sil2100> Awww, with this internet I'm too slow ;)
[12:36] <sil2100> Power is back, yeah
[12:37] <sil2100> Let me try getting the train back to shape
[12:44] <jibel> sil2100, nuclearbob confirmed the black screen issue. It happens often on reboot since yesterday
[12:46] <sil2100> jibel: on reboot even? Crap
[12:46] <sil2100> That's a big blocker then
[12:46] <sil2100> (IMO)
[12:46] <sil2100> Mirv: found the issue... it seems after Robert's changes, reconfigures are broken in overall
[12:46] <sil2100> Mirv: since they're impossible to work in the current state of the code
[12:46]  * sil2100 tries to fix
[12:47] <sil2100> Mirv: I would normally opt for a revert, but not sure if the new code didn't introduce some changes in the config files
[12:47] <sil2100> And I don't want to break everything (tm)
[12:47] <Mirv> right
[12:48]  * sil2100 wonders why normal silo assignments worked though
[12:49] <bzoltan_> Mirv: sil2100: I missed about 2 hours. Is there any news about the silo reconfigurations?
[12:51] <Mirv> bzoltan_: just the above, sil is looking into the brokennes. we could assign a new silo and delete old one if in a hurry.
[12:51] <bzoltan_> Mirv:  far from hurry ... I can test the silo during the night without the gles packages
[12:52] <Mirv> true
[12:58] <sil2100> Ah, I see why normal assignments work, yeah
[13:05] <sil2100> Fix is on the ways
[13:05] <sil2100> *way
[13:26] <balloons> cihelp, I need a parameter adjusted on a jenkins job for the help app
[13:36] <plars> balloons: what needs changing?
[13:37] <balloons> plars, can you swap the pyflakes parm to pyflakes3?
[13:37] <plars> balloons: sure, will do
[13:42] <sil2100> Mirv, bzoltan_: waiting for CI to check the branch, then I merge and try redeploying the fix
[13:42] <Mirv> \o/
[13:46] <bzoltan_> sil2100: thanks mate, you rock as always
[14:01] <mzanetti> sil2100, not sure about the status on that issue, just wanted to make sure you don't forget about the reconfig vivid/15 when it's resolved :)
[14:10] <sil2100> mzanetti: ACK :)
[14:10] <mzanetti> thanks :)
[14:10] <rvr> oSoMoN: Silo 8 is approved.
[14:10] <rvr> sil2100: ^^
[14:11] <rvr> sil2100: You can respin the new image when you want :)
[14:11] <oSoMoN> rvr, awesome, thanks!
[14:16] <Mirv> ogra_: ack oxide version bumps? https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/lastSuccessfulBuild/artifact/webbrowser-app_packaging_changes.diff ^
[14:21] <sil2100> \o/
[14:22] <sil2100> Once webbrowser migrates, let's have a new image
[14:22] <sil2100> On the other hand...
[14:22] <sil2100> There's that serious regression anyway
[14:23] <sil2100> So not sure if it makes sense, hm
[14:23] <sil2100> jibel: do you guys know which component can be responsible for the black screen issue?
[14:23] <jibel> sil2100, no
[14:23] <jibel> sil2100, nuclearbob filed bug 1435871
[14:24] <jibel> ah it's duplicated already
[14:24] <sil2100> Oh
[14:26] <jibel> 'undecided' looks inappropriate
[14:26] <oSoMoN> ogra_, hey, I need a core-dev ack for trivial packaging changes in silo 8: https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/89/artifact/webbrowser-app_packaging_changes.diff
[14:28] <sil2100> Mirv: keep us updated on this bug please ;)
[14:29] <Mirv> sil2100: yep, the current patches regressed autopilot tests and now albert gave me two more to try which are building now. although I wonder if libusermetrics should be added to the bug too since it appeared with an update of that, even if it triggers some old Qt bug.
[14:29] <ogra_> oSoMoN, Mirv ACK
[14:30] <Mirv> acketi ack
[14:35] <Mirv> sil2100: added autopilot and libusermetrics to the bugreport with "Incomplete" since the former may be affected and the latter apparently triggered the bug even if technically didn't do anything wrong
[14:38] <oSoMoN> ogra_, Mirv: thanks!
[14:38] <Mirv> sil2100: oSoMoN ^ oh right.. Final beta freeze until Thursday evening :(
[14:39] <oSoMoN> yeah, no worries, at this point it’s not really that urgent
[14:48] <sil2100> hmmm
[14:48] <sil2100> Yeah
[15:07] <Mirv> sil2100: I'm again at https://ci-train.ubuntu.com/job/ubuntu-landing-018-1-build/122/console ... train digging the older version, seeing it's built and continuing without waiting.. I've tried build, build with specifying packages and build with specifying packages + force
[15:10] <Mirv> hmm, was it watch_only then plus specifying packages that was needed..
[15:12] <sil2100> hm
[15:15] <balloons> plars, how's the change look?
[15:15] <plars> balloons: I had to rerun it, just checked and it's merged now
[15:16] <plars> balloons: Can you give it a try or do I need to restart a job for you?
[15:16] <plars> balloons: I'll be curious to see if it does what you need
[15:27] <bregma> trainguards, reconfiguring my silo always fails claiming its PPA has changed underneath it... am I doing something wrong or is it a known bug?
[15:27] <bregma> (line 46, silo 29)
[15:31] <sil2100> bregma: yeah, please see the topic ;)
[15:32] <sil2100> bregma: the fix is ready but I'm witingn for webops to actually deploy that for us
[15:32] <sil2100> Since we can't redeploy oursleves
[15:32] <sil2100> *ourselves
[15:33] <balloons> plars, yes i'll check ty
[15:33] <sil2100> ogra_: anything against building a new vivid image now?
[15:33] <ogra_> no, go ahead
[15:33] <sil2100> Actually, wait, unity8 still didn't migrate
[15:34] <sil2100> Argh, boottest regression
[15:34] <sil2100> Saviq: ^
[15:35] <sil2100> Saviq: so, unity8 fails to migrate due to a boottest failure: https://jenkins.qa.ubuntu.com/job/vivid-boottest-unity8/lastBuild/console
[15:36] <sil2100> Not sure what's wrong, the log looks a bit bloated
[15:36] <sil2100> cihelp: can you guys help me interpret the above boottest failure? ^
[15:38] <fginther> sil2100, there's evidence of a race condition with apt here, I've restarted the test
[15:38] <sil2100> fginther: thanks, fingers crossed it'll pass now :)
[15:38] <fginther> "E: Unable to lock directory /var/lib/apt/lists/"
[15:43] <sil2100> jibel, davmor2, rvr, popey: since robru is on holidays and there's not much to report (I suppose), let's skip today's evening meeting
[15:44] <sil2100> We might do that for most of the week
[15:44] <sil2100> If, of course, there's nothing urgent
[15:44] <jibel> sil2100, works for me
[15:44] <jibel> sil2100, only thing urgent is to build a new image :)
[15:44] <sil2100> The vivid image I'll be kicking as soon as unity8 migrates
[15:44] <jibel> ok
[15:44] <sil2100> Since it was blocked on boottesting, maybe now it'll pass
[15:46] <sil2100> bregma, Mirv, bzoltan_, mzanetti: I filled in the RT and poked webops, I hope they'll redeploy it soon
[15:47] <sil2100> bregma, Mirv, bzoltan_, mzanetti: regarding the CI Train issues with reconfigure
[15:49] <davmor2> sil2100: powermongery has gone to your head, I should never of made you admin ;)
[15:53] <sil2100> davmor2: muhahaha
[15:57] <sil2100> camako: hey! There might be a problem with releasing the new mir as we're in beta freeze, and I think mir is somehow partially seeded on the desktop
[15:59] <camako> sil2100, I thought we were stabilizing vivid for the rtm sync.. How much longer does the freeze continue?
[16:00] <sil2100> camako: we are, but the beta freeze means that there's a hard lock on the archive and things like mir can get pushed to unapproved automatically
[16:00] <sil2100> Then we'll have to poke the archive admins
[16:02] <camako> sil2100, so I'm confused. How are we stabilizing if we can't land? Is this only for a day or two or until Vivid is released (late April)?
[16:02] <sil2100> bregma: you should be able to reconfigure now
[16:02] <ogra_> camako, the beta freeze lasts til the beta image is fully tested
[16:02] <cjwatson> sil2100: s/archive admins/release team/
[16:02]  * bregma gives reconfiguration a go
[16:03] <sil2100> camako: we can't do much against archive related procedures
[16:03] <balloons> plars, is the parms line the same? B10pyflakes?
[16:03] <ogra_> it is in place to make sure the image content cant change ... something that touch catches on the silo level ... distro can only do it by freezing the whole archive
[16:03] <cjwatson> camako: it doesn't mean you can't land, it means landings require additional manual approval to make sure they don't disrupt image preparations
[16:03] <cjwatson> camako: describing it as "can't land" is a gross mischaracterisation
[16:03] <mzanetti> sil2100, ok, thanks!
[16:04] <sil2100> mzanetti: should be reconfigured :)
[16:04] <camako> sil2100, cjwatson... sorry on a hangout atm.. Will resume discussion in a bit
[16:04] <sil2100> jibel: unity8 boottesting passed o/
[16:10]  * sil2100 waits for the next migration
[16:22] <sil2100> unity8 migrated, let me kick the new image
[16:25] <imgbot> [16:27] <dbarth_> o/ hey trainguards, can i have a silo on line 62 ?
[16:28] <sil2100> dbarth_: sure
[16:28] <sil2100> dbarth_: for rtm?
[16:31] <dbarth_> sil2100: yes, please
[16:31] <dbarth_> (sorry forgot about the target release column)
[16:34] <balloons> plars, things are still failing; and I don't see the default parms changed at all
[16:55] <pmcgowan> sil2100, jibel we should hold off the vivid regression ass until we figure out the multiple audio issues in the latest images
[16:55] <pmcgowan> pass not ass
[17:45] <plars> balloons: do you happen to have a link, I'll take a look. Probably the jobs need to be redeployed
[17:51] <balloons> plars, 91.189.93.70:8080/job/help-app-ci
[17:55] <imgbot> [17:55] <imgbot> [18:43] <rvr> mandel: I'm testing silo 0 for rtm (ciborium). pot file needs update, because "Unmounting" is marked for translations, but is not available in Launchpad.
[18:55] <rvr> [mandel] idle 125:43:47 ... I guess he's on holidays.
[19:00] <rsalveti> rvr: nops, he's around
[19:31] <rvr> rsalveti: mandel: As you can see, silo 0 was approved.
[19:34] <rsalveti> rvr: great, thanks
[19:36] <camako> sil2100, cjwatson, so last comment was we can land on vivid. What are the caveats? Do we need to ask anyone for permission etc?
[20:23] <veebers> trainguards, ping can I get 004 published please? :-)
[20:29] <pmcgowan> rsalveti, sil2100 are we not doing rtm proposed builds?
[20:29] <rsalveti> pmcgowan: not by default, no
[20:29] <pmcgowan> rsalveti, how come?
[20:30] <rsalveti> pmcgowan: disabled in cron-job to avoid having images without any changes
[20:30] <rsalveti> pmcgowan: we can enable cron anytime, or just build new images when we land new changes
[20:30] <pmcgowan> rsalveti, we should kick some as there have been a number of landings
[20:30] <rsalveti> sure, will do
[20:30] <pmcgowan> was waiting for them
[20:30] <pmcgowan> thanks
[20:32] <rsalveti> robru: can you help me with https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-000-2-publish/32/console ?
[20:32] <rsalveti> this was a job that got build via a sync
[20:39] <elopio> rsalveti: on the topic it says that robry is on vacation.
[20:39] <rsalveti> crap, indeed
[20:39] <rsalveti> maybe cyphermox can help me with that then
[20:39] <rsalveti> cyphermox: trying to publish silo 000/rtm https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-000-2-publish/32/console
[20:55] <cyphermox> hum, why is it 000?
[20:55] <cyphermox> I thought that one was meant for testing and all
[20:57] <rsalveti> cyphermox: nops, it's a valid silo
[20:58] <cyphermox> I see
[20:58] <cyphermox> rsalveti: did you change anything in the silo config since you first requested it?
[20:59] <rsalveti> cyphermox: nops
[20:59] <cyphermox> I'm trying to know why it would be acting this way
[21:01] <AlbertA> cihelp: it looks like mir amd64 builds done in cloud-worker-15 always time out, for example: https://jenkins.qa.ubuntu.com/job/mir-vivid-amd64-ci/1337/consoleFull
[21:02] <AlbertA> cihelp: any ideas?
[21:02] <cyphermox> rsalveti: clearly, this is broke
[21:05] <cyphermox> thar.
[21:05] <cyphermox> I fudged it to agree to publish
[21:09] <thomi> AlbertA: I'll take a look
[21:11] <veebers> cyphermox: hey, are you able to publish silo 004? :-)
[21:17] <cyphermox> veebers: what kind of silo?
[21:20] <veebers> cyphermox: bugfix for autopilot
[21:24] <cyphermox> no, I mean is that a rtm silo or what?
[21:24] <veebers> cyphermox: oh sorry, vivid
[21:32] <veebers> ugh, fixing that now
[21:34] <veebers> cyphermox: sorry about that, the MP has been fixed so it can be published again
[21:52] <robru> cyphermox: rsalveti: reviewing the logs, it always as though mandel attempted a new sync which cleared the local silo state, but failed because the sync source had freed. Then your attempts at builds were just watch-only's which doesn't have enough teeth to regenerate the needed state.
[21:53] <robru> cyphermox: rsalveti not sure why the build by mandel didn't fall back to distro, that's a feature that is supposed to exist, please file a bug against lp:cupstream2distro and I'll fix it next week when I'm back
[21:56] <robru> "It appears as though" stupid swype.
[21:58] <robru> cyphermox: rsalveti anyway this is the culprit: https://ci-train.ubuntu.com/view/1.%20Build/job/ubuntu-rtm-landing-000-1-build/153/console that's definitely a bug, it should sync from distro if the source silo has freed
[21:58]  * robru back to vacation ;-)
[22:11] <veebers> cyphermox/trainguards any idea on who can do that (or what to do here) we had barry ack the package changes in the merge to trunk MP
[22:23] <rsalveti> robru: great
[22:34] <sil2100> robru: thanks for the investigation, I'll try to look at it tomorrow then ;)
[22:35] <cyphermox> veebers: I will, I was busy fixing dinner :)
[22:38] <cyphermox> oh crap
[22:39] <veebers> cyphermox: ah cool, sorry to be impatient :-)
[22:39] <cyphermox> hm, did you have a freeze exception for this?
[22:40] <veebers> No we didn't. I was told (by robru) that as it was a bug fix for autopilot it was required.
[22:41] <cyphermox> ah, I see
[22:42] <veebers> cyphermox: does this complicate things? (perhaps I messed up?)
[22:42] <cyphermox> no, I had a moment of doubt, that's all
[22:48] <veebers> ah ok, thanks for sorting this cyphermox :-) I hope you get to enjoy your dinner soon!
[22:49] <cyphermox> ahaha already done
[22:49] <cyphermox> we were tired so I threw together some pasta with a bottled sauce :P
[22:54] <cjwatson> camako: if you're adding features, you should follow https://wiki.ubuntu.com/FreezeExceptionProcess; otherwise, uploads will be automatically held for approval and the release team notified, though you can ask on #ubuntu-release if you need to have something expedited
[22:54] <cjwatson> camako: (speaking as an ex-release-team-member)
[23:00] <sil2100> o/
[23:01] <veebers> cyphermox: heh, sounds more interesting than the brown rice and chicken breast I've been boring myself with recently :-)
[23:07] <cyphermox> I was supposed to make some chili with the slow cooker but I was so busy I forgot to get started early enough for food to be ready on time
[23:10] <veebers> oh man, I totally want to get into using a slow cooker. Especially now that the season is cooling down
[23:12] <veebers> cyphermox: hey I see that the autopilot package is in the unapproved queue in #u-release, what needs to happen next?
[23:13] <cyphermox> probably wait until after beta is released to be let in, or you may ask in #u-release for it to be allowed in
[23:16] <veebers> cool thanks, I'll ask and see what happens :-)
[23:40] <cjwatson> (FYI autopilot was auto-accepted and didn't need manual interaction)
[23:41] <cyphermox> cool, thanks for letting us know
[23:48] <camako> cjwatson, thanks. We are not adding features. This is strictly a bug fix release.
[23:50] <cjwatson> camako: yeah, don't tell me though, I'm ex-release-team :)
[23:50] <cjwatson> camako: in that case, just land and then ask the release team to review (or wait for them to get round to it in their queue)
[23:50] <cjwatson> camako: it may have to wait until after beta in any event, but that's only a couple of days