[00:32] <RAOF> Ok. *That* was a race in my code :)
[02:38]  * RAOF heads due luncheon
[07:39] <RAOF> Ok.
[07:39] <RAOF> Ok.
[07:39] <RAOF> OK.
[07:40] <RAOF> That *should* fix all the races in https://code.launchpad.net/~raof/mir/fix-deadlock-in-glib-alarm/+merge/266682
[10:21] <ogra_> poor duflu ... seems i actually stirred up something with my input delay bu
[10:21] <ogra_> *bug
[10:22] <duflu> ogra_: The earlier we know about them the better. You're doing us a great service :)
[10:22] <ogra_> (looks like you are getting from one rabbithole into the next all the time)
[10:22] <duflu> ogra_: Yeah sometimes you just need to stop looking
[10:22]  * duflu -> EOD
[10:22] <ogra_> heh
[10:22] <ogra_> enjoy
[11:50] <alan_g> greyback: When you have a moment, could you have a look. (I can't imagine my qtmir changes caused it but it is worrying). https://jenkins.qa.ubuntu.com/job/qtmir-wily-amd64-ci/73/console
[11:51] <greyback> looking
[11:51] <greyback> alan_g: doubt it's your fault, looks like the dbus test harness is failing
[11:53] <greyback> pete-woods: hey, any ideas how we can debug that ^^
[11:53] <greyback> it's using dbusmock, and failing with C++ exception with description "Process [python3] for service [com.canonical.powerd] failed to appear on bus" thrown in the test fixture's constructor.
[11:55] <alan_g> greyback: thanks
[12:49] <pete-woods> greyback: looking
[12:49] <pete-woods> (sorry, was having lunch)
[12:50] <pete-woods> greyback: does this happen if you do a debuild locally?
[12:51] <pete-woods> this can happen if the build server is super heavily loaded
[12:52] <pete-woods> it waits 5 seconds for the python process to start
[12:52] <pete-woods> that's probably not enough, actually
[12:52] <greyback> pete-woods: not happening locally for me anyway
[12:52] <pete-woods> (it uses QSignalSpy::wait)
[12:52] <pete-woods> which has a default timeout of 5 seconds
[12:53] <pete-woods> this should maybe be upped to 30 seconds
[12:53] <greyback> you'd think 5 secondsis enough to bring up python. But if you've seen it randomly on servers, it'll do no harm to bump it
[12:53] <pete-woods> as starting a new python process can take quite a while on a low memory / loaded system
[12:53] <greyback> alan_g|lunch: could you retry the build, just to see
[13:02] <alan_g> greyback: ack