[08:13] <Laney> moooooooooooorning
[08:56] <mlankhorst> morning
[08:58] <sil2100> Morning
[09:01] <Laney> sup
[09:01] <Laney> sil2100: don't override my reviews!
[09:02] <sil2100> Laney: I didn't top-approve! ;)
[09:02] <Laney> :P
[09:02] <sil2100> Laney: I just approved locally, since the changes looked fine ;p
[09:02] <Laney> my new branch for that is almost done
[09:02] <sil2100> Mirv: hello! How are the stacks today? I see a lot of gray ;p
[09:03] <sil2100> Laney: awesome, maybe then I can do a review at least... ;p
[09:03] <Mirv> sil2100: they're just in progress, not otherwise
[09:03] <Mirv> sil2100: as you probably know, the overview doesn't say much about the current tick ongoing
[09:04] <Mirv> sil2100: a lot of stuff (indicators + platform) would now require newer mir
[09:04] <Mirv> and of course unity, sdk etc depend on those
[09:05] <Mirv> so it'd look like it's not possible to even consider individual stacks much before the whole situation starts to be resolved, starting from publishing mir
[09:06] <Mirv> sil2100: did you get any update yesterday evening about how's the unity8/mir going?
[09:07] <Mirv> I see there were another unity8/unity-mir releases, just wondering if it's now "done"
[09:34] <sil2100> Mirv: Ricardo wrote to me in the morning that he needs unity8 landing with ubuntu-keyboard
[09:35] <sil2100> Mirv: but I see services is red...
[09:35] <sil2100> Mirv: ah, some AP failure, I guess it's more or less ok
[10:05] <sil2100> Mirv: eh
[10:05] <sil2100> Mirv: the problem now is, Ricardo wanted to release unity8, but that depends on mir, and I have no idea what's the current state of that stack - if we can release it or not
[10:07] <sil2100> Mirv: it seems we missed this tick, but I guess it's better this way
[10:09] <Mirv> sil2100: yeah, me neither regarding mir, plus I guess we need explicitly the permission from asac/didrocks anyhow
[10:10] <sil2100> Mirv: let me use the time of the missed tick and get the stacks into shape - I'll try fixing platform
[10:13] <sil2100> Mirv: right, although from what Ricardo mentioned, it should be ok to release unity8 as everyone was aware of it needing release - but I'm reluctant to do that without releasing mir, mirslave and platform, as you never know what might be dwelling in there
[10:13] <Mirv> sil2100: platform looked like it was wanting just the newer mir as well
[10:13] <sil2100> Mirv: yep, I rebuilt the pacakges
[10:13] <Mirv> sil2100: right, ok
[10:14] <sil2100> Mirv: I also noticed that the DNS issue seems to be happening a lot more to the intel machine
[10:45] <sil2100> Mirv: and great, both test machines are unavailable again...
[10:46] <sil2100> Mirv: this process is getting less and less automated
[10:54] <Mirv> sil2100: we can automate the constant restarting and rebooting of everything...
[10:55] <Mirv> sil2100: so I assume no breakthroughs were made yesterday in fixing the problems yet
[10:56] <Mirv> sil2100: both running again now it seems?
[10:56] <sil2100> Yes, I re-ran the slaves
[10:57] <sil2100> But still, if one is busy with other stuff and doesn't monitor the autopilot jobs, it might be missed and blocked
[10:57] <Mirv> sil2100: right. funny that the same log file has 09:16:46 and then 10:49:32
[10:57] <Mirv> sil2100: yes, it's more like constant refreshing and going over of everything, and still the slowdowns make it so that a full tick doesn't run in 4 hours, more like 5-6 hours minimum
[10:59] <sil2100> Indeed
[12:16] <didrocks> sil2100: hey!
[12:16] <didrocks> around?
[12:23] <sil2100> didrocks: yep
[12:23] <sil2100> didrocks: I just finished lunch
[12:23] <sil2100> didrocks: I had a question related to unity8 release
[12:23] <sil2100> didrocks: since I got an e-mail from Ricardo about releasing unity8 + ubuntu-keyboard
[12:23] <sil2100> didrocks: but I was worried of pressing 'publish' without publishing mir etc.
[12:24] <sil2100> Oh, I see you already force-published?
[12:25] <sil2100> didrocks: a mir+mirslave release in the same time is not needed with this?
[12:26] <didrocks> sil2100: I didn't publish
[12:26] <sil2100> didrocks: also, Ricardo wanted to release ubuntu-keyboard at the same time, I see you re-ran the check job - I guess a force publish would be enough, as there was only one failure
[12:26] <sil2100> hmmm
[12:26] <didrocks> sil2100: you did use daily-build-next to build unity8, right?
[12:26] <didrocks> as the mir version is busted in daily-build ppa
[12:27] <sil2100> I didn't do anything, I wonder who published the unity8 stack :| It was waiting yellow till now, thought you did the publishing now
[12:27] <didrocks> urgh
[12:27] <didrocks> :/
[12:27] <didrocks> no, nobody publish it
[12:27] <didrocks> and there is no unity8 in it
[12:27] <sil2100> Ah
[12:27] <pitti> Good morning
[12:28] <sil2100> I get it now, I see that it is just green without anything, nvm then
[12:29] <sil2100> didrocks: aaarrrghhh
[12:29] <sil2100> didrocks: Ricardo's branch didn't get merged
[12:30] <sil2100> didrocks: and the unity8 stack being yellow made me think that it was merged in, as Ricardo said it as if it's in trunk already - but it was not
[12:30] <sil2100> Failed on CI
[12:33] <sil2100> didrocks: which Mir am I supposed to use to build unity8 ? The mir in daily-build shouldn't be that broken now, as I see mirslave tests passed - the revert got in
[12:33] <Mirv> sil2100: autopilot-intel seems offline again to jenkins
[12:33] <sil2100> Mirv: ah come oooooon :| :| :|
[12:35] <lool> qengho: Ah thanks for the chromium-browser fix; it was super annoying
[12:35] <sil2100> Mirv: I restarted the slave
[12:58] <qengho> lool: yeah, sorry about it altogether. On the good side, it has tests to catch things like that now.
[14:55] <sil2100> didrocks, asac: unity8 finished, but intel failed because of DNS issues - I guess we can publish anyway, or I can re-run the testing if you guys are on a meeting anyway
[14:56] <sil2100> I'll re-run it for now
[14:56] <sil2100> Just the check jobs
[14:57] <sil2100> didrocks: re-ran with foo, hopefully we'll get more lucky with intel this time
[14:58] <didrocks> sil2100: yeah, I saw that
[14:58] <didrocks> sil2100: but I was monitoring the armhf build
[14:58] <didrocks> so have to look at the new job
[15:01] <didrocks> sil2100: retoaded told me that all DNS issues were supposed to be fixed
[15:01] <didrocks> sil2100: please reping him then
[15:01] <didrocks> asac: the DNS issues are still slowing us down…
[15:02] <sil2100> didrocks: I poked jibel today already, will poke retoaded as well
[15:03] <didrocks> thanks
[15:04] <didrocks> sil2100: still busted, please escalate
[15:04] <didrocks> asac: I will ignore intel result, the DNS block us
[15:04] <didrocks> I'll publish
[15:06] <sil2100> ;/
[15:06] <jibel> sil2100, unfortunately there is nothing I can do on DNS issues, retoaded only can help :/
[15:06] <sil2100> jibel: ACK
[15:07] <sil2100> didrocks: actually it looks that there was a test failure on intel this time?
[15:07] <didrocks> sil2100: no, same issue
[15:08] <sil2100> didrocks: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. is the same reason?
[15:08] <sil2100> ACK :)
[15:08] <didrocks> it's just a X crash
[15:08] <didrocks> anyway publish
[15:08] <didrocks> asac: everything is in proposed
[15:34]  * Laney pushes some branches for sil2100 to get his teeth into
[16:45] <tjaalton> slomo: looks like new gstreamer doesn't handle asx radio streams? (tried totem & rhythmbox)
[17:08] <Laney> right
[17:09] <Laney> off until tuesday!
[17:12] <Laney> sil2100: one thing to do if my branch gets approved ;-) would be to go through the settings that aren't working and disable them
[17:12] <Laney> follow the few examples I did there
[17:13]  * Laney waves
[17:15] <jbicha> Laney: I wonder if any other release team member will touch bug 1092719
[17:15] <ubot2`> Launchpad bug 1092719 in gnome-disk-utility (Ubuntu) "FFe: Update gnome-disk-utility to 3.8" [Wishlist,Confirmed] https://launchpad.net/bugs/1092719
[17:15] <Laney> jbicha: oh, bah
[17:15] <Laney> poke ScottK
[17:15] <Laney> I'm happy with it in principle
[17:16] <jbicha> ok I'll give him a try
[17:16] <Laney> jbicha: also
[17:16] <jbicha> have a good weekend
[17:16] <Laney> DAMN, YOU KEPT ME
[17:16] <Laney> did you see that I pinged you yesterday?
[17:16] <Laney> lib...something broke the gstreamer bad build because of a pcfile change
[17:16] <Laney> you should check its other rbuilddeps don't have issues
[17:17] <jbicha> ok I can check whether the rdepends still build at least
[17:18] <Laney> yes, they'll fail to build if there is a problem
[17:18] <Laney> the fix is trivial, see the diff I did
[17:18] <Laney> really bye now
[17:18] <Laney> don't break stuff ;-)
[17:56] <cyphermox> sil2100: you still touching the stack transitions?
[17:56] <cyphermox> like, saucy and all, config and deploying?
[20:13] <sil2100> cyphermox: the stack transitions are ready, but I was waiting for stuff to get released before I do the transition
[20:14] <cyphermox> sil2100: it's done now
[20:15] <cyphermox> we ended up killing all the jobs that started around 1800 UTC, did the deploys, etc.
[20:15] <sil2100> cyphermox: did you redeploy?
[20:15] <cyphermox> yes
[20:15] <sil2100> cyphermox: what about history? Did you move it on mangers?
[20:16] <cyphermox> I just sent an email about the details, I should go find jibel to create the views
[20:16] <cyphermox> what history?
[20:18] <sil2100> cyphermox: the "Copying autopilot results from head to raring" section - I'll do that then
[20:18] <sil2100> cyphermox: did you fill in the RT for the view, or should I do that?
[20:19] <sil2100> cyphermox: I'll copy the history, no worries
[20:19] <sil2100> Doing that now
[20:22] <sil2100> Laney: can you point me to the branch ;)?
[20:25] <sil2100> cyphermox: I'm also filling in the RT
[20:25] <cyphermox> ack, but jibel is already aware
[20:25] <sil2100> Ah, ok
[20:25] <cyphermox> I should go seem him, will as soon as I have two seconds
[20:26] <sil2100> cyphermox: ok, so I let you deal with this one
[20:27] <sil2100> didrocks: retoaded says that the intel machine will be fixed with the DNS issues pretty soon, as it's one of the last leftover machines that need migrating to the new sub-network
[20:27] <cyphermox> sil2100: ack
[20:28] <sil2100> Laney: found the branch, reviewing
[20:28] <slomo> tjaalton: there should be no difference about that between 1.0.x and 1.1.x... please file a bug with a testcase
[20:34] <tjaalton> slomo: ok
[20:57] <tjaalton> slomo: filed #1224681