[01:03] <bschaefer> RAOF, alright, merged trunk and fixed some minor things
[01:03] <bschaefer> i think its ready... but you never know :)
[01:03] <bschaefer> passing locally for me
[01:04] <RAOF> SHIP IT!
[01:05] <RAOF> Or at least run CI against it :)
[01:08] <bschaefer> RAOF, :)
[02:02]  * bschaefer wonders how that wasnt caught
[02:15] <duflu> bschaefer: If you mean that CI failure... it only fails sometimes. And even then only in CI. Never when you run it manually :/
[02:15] <duflu> Annoyingly difficult to fix
[02:15] <duflu> Something about our CI machines is very different to the team's own machines
[02:17] <bschaefer> duflu, well i guess it compiled somehow on my end
[02:17] <bschaefer> but shouldnt have :)
[02:17]  * bschaefer started getting errors
[02:17] <bschaefer> and idk how it happened haha
[02:18] <duflu> bschaefer: Yeah it compiles and passes tests for everyone. Except sometimes fails that test only in CI
[02:18] <bschaefer> duflu, haha... well i think this case it was my fault :)
[02:19]  * bschaefer would not like that
[02:19] <duflu> OK, different topic then
[02:19] <bschaefer> yeah
[02:19] <bschaefer> duflu, but i've seen that
[02:59] <duflu> Heh. If you want something to land quickly just get me to not like it. Then a large number of people will argue the opposite and your branch gets rapid approval
[02:59] <duflu> Works every time
[03:41]  * bschaefer wonders why CI seems to hate me
[03:41] <bschaefer> i think it just blew up...
[03:48] <duflu> bschaefer: I only just fixed that failure you reported. Any CI jobs started in the past few hours will fail with that error that's already fixed. Try again.
[03:48] <bschaefer> duflu, Well it failed by saying the nodes went off line :(
[03:48] <bschaefer> https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid-armhf/3569/console
[03:48] <duflu> Woo. No that's not me
[03:48]  * bschaefer hasnt ever seen that
[03:48] <bschaefer> haha
[03:48]  * bschaefer hopes it turns back on
[03:51] <duflu> bschaefer: The universe is telling you to EOD
[03:51] <bschaefer> haha
[03:51] <bschaefer> duflu, just wanted to see the SUCCESS
[03:51] <bschaefer> before i headed off
[03:52] <duflu> I know. It's a trap. But having the self control to log off is a good way to stay sane
[03:53] <bschaefer> true, just watching tv and checking my email every now and then
[03:53] <bschaefer> not much working going on :)
[03:57] <duflu> Such is the way in this always connected world.
[03:58] <bschaefer> true, hard to log off irc
[03:58] <duflu> bschaefer: Yeah other branches are dying in CI too. Not something likely to be fixed quickly
[03:59] <bschaefer> yeah o well, its all passing locally now (double checked) soo
[03:59] <bschaefer> im like 99% sure its done
[05:03] <RAOF> Yeeeeeeeeeees!
[05:03] <RAOF> Finally CI passes!
[08:56] <duflu> greyback: Are you aware of any touch test case that has stretchy resize still?
[08:56] <duflu> Or is it only desktop?
[08:59] <duflu> Never mind. Found one bug at least
[09:00] <greyback> duflu: it's all qml/qtmir's fault, where they don't wait for a resized buffer before drawing it at the new size.
[09:01] <duflu> greyback: Yeah I know what to fix, just wanted a manual test case
[09:01] <duflu> Found them
[09:08] <duflu> Crap. Except I lost my phone build environment and may not have enough time to rebuild it this week
[09:20] <greyback> duflu: hey, will you have that early buffer release in qtmir work ready to propose any time soon?
[09:21] <duflu> greyback: It's painfully slow. The Mir fix landed yesterday and then I had to revert it today. Now waiting on CI to get fixed again so I can find out why it fails only in CI
[09:22] <greyback> duflu: ah ok. I noticed your fix landed, didn't see it had to be reverted.
[09:22] <duflu> So I'm now donating my Friday evening to an unrelated QtMir fix
[09:22] <greyback> the stretched frames issue?
[09:23] <duflu> greyback: Yeah generally "never stretch"
[09:23] <greyback> duflu: ok. Your thoughts are welcome
[09:24] <greyback> mainly shell needs to not animate towards a resized-frame, until a frame with that size has been swapped by the client
[09:25] <greyback> right now we fire resize, do our animation on the previous frame, then hope the resized frame is ready at the end of the animation
[10:08] <duflu> greyback: Happy Friday. I'm off to make dinner... https://code.launchpad.net/~vanvugt/qtmir/unstretch/+merge/268724
[10:34]  * alan_g discovers the diagnostics from connection failures get eaten in the client callstack.
[10:59] <alan_g> Actually, they don't even reach the client
[11:19] <kgunn> is it worse to be lost or eaten
[11:24] <Mirv> I finally got archive admin approval, meaning Mir 0.15 is now in wily
[11:24] <Mirv> (-proposed)
[11:25] <Mirv> AlbertA: ^
[11:27] <kgunn> mmm
[11:27] <alan_g> kgunn: the reporting is misleading and confused me. (And I have touched most of this code.) Going to MP a small cleanup.
[11:29] <kgunn> alf: just in case, so you know, silo 9 where you delivered that hot fix for the emulator - is a dual landing, since mir15 landed....i'm gonna pull it out of there
[11:29] <kgunn> and land that thing in isolation to vivid+
[11:30] <kgunn> does that make sense
[11:34] <alf> kgunn: ok, so we will eventually need to include the fix in 0.15.x (or 0.16 if we get to it)
[11:35] <kgunn> alf: +1 we should just have 2 silos, one for vivid+o hotfix to 14, then wily for 15
[11:36] <kgunn> i can take care of "paperwork"
[11:36] <kgunn> just wanted you to know
[11:36] <alf> kgunn: ack, thanks
[11:36] <kgunn> alf: but thanks for the reminder it wasn't naturally in 15 ;)
[11:36] <kgunn> i forgot
[11:37] <kgunn> we haven't taken a cut off for 16 yet have we ?
[11:37] <kgunn> and is this change already on trunk ?
[11:38] <alf> kgunn: we haven't cut off for 16, change is in trunk
[11:47] <kgunn> cool
[14:12] <AlbertA> Mirv: ummm I acutally parked that because
[14:12] <AlbertA> we wanted 0.14.1 to land first....
[14:13] <AlbertA> oh gosh....what a mess
[14:16] <AlbertA> Mirv: can we revert mir 0.15 from wily-proposed?
[14:26] <Mirv> AlbertA: oh, I parsed your message wrongly in that case. but it was FF yesterday, if you'd cancel 0.15 now you wouldn't get it in without FFe. isn't it easier to do a maintenance release of 0.15 with 0.14.1 changes added on top of it?
[14:26] <AlbertA> Mirv: the problem is sync to vivid+overlay.... but we'll figure it out thanks
[14:27] <Mirv> AlbertA: yes it was already discussed a bit so that silo 9 would be vivid+overlay only and you'd sort it out
[14:27] <Mirv> since silo 9 also has a small mir fix
[15:49] <alan_g> camako: did you intend to approve https://code.launchpad.net/~alan-griffiths/mir/simplify-connect-code/+merge/268740?
[15:50] <camako> alan_g, yes... reapproved