[05:56] <dkessel> DanChapman: good morning. I want to help with getting the jenkins server for flavors up. If there's anything I can do to help, please let me know.
[05:58] <knome> ah, so that's the latest news?
[05:58] <knome> eg. not trying to set up $something_else for flavors?
[05:58] <knome> or is jenkins an app name?:)
[05:59] <dkessel> jenkins is a build server software
[05:59] <dkessel> morning knome :)
[05:59] <dkessel> yup, that seems to be the state of things
[06:00] <knome> mmhm
[14:12] <kenvandine> alesage, not sure that's the same bug
[14:12] <kenvandine> alesage, i'm seeing it on mako
[14:12] <kenvandine> alesage, oSoMoN saw the same problem yesterday on krillin with vivid
[14:12] <kenvandine> alesage, for the webbrowser-app
[14:20] <oSoMoN> alesage, and for the record it’s not the first time I’m seeing this issue, although I don’t remember when I saw it first
[14:22] <kenvandine> hey jgdx
[14:22] <jgdx> hey kenvandine
[14:22] <kenvandine> oSoMoN, what is bugging me is that it gets the system in a bad state
[14:22] <kenvandine> i can't even run a single test that uses keyboard.write after it fails the first time
[14:22] <kenvandine> but manual use of the osk works fine
[14:22] <kenvandine> but nothing with autopilot that uses the osk works
[14:23] <jgdx> kenvandine, you're in that state now?
[14:23] <kenvandine> yes
[14:23] <oSoMoN> definitely sounds like an issue in autopilot itself
[14:23] <kenvandine> i don't think so
[14:23] <kenvandine> since it persists across autopilot runs
[14:23] <kenvandine> until reboot
[14:23] <oSoMoN> do we have any autopilot expert around that could help investigate the issue?
[14:24] <kenvandine> alesage, suggested talking to veebers, but he's not around right now
[14:25] <kenvandine> oh wait... somethings crashing
[14:25] <kenvandine> but not leaving .crash files
[14:27] <kenvandine> apport-noui-_var_crash__usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_socket-demangler.32011.crash.log
[14:27] <kenvandine> maybe it is mir related
[14:27] <kenvandine> but the socket demangler stuff hasn't landed in vivid overlay... so maybe not
[14:30]  * kenvandine cleans up logs and stuff and tries again
[14:32] <jgdx> would help to know what's between autopilot and the osk :)
[14:33] <alesage> kenvandine, oSoMoN I'm listening--if it's a mir thing racarr was helping before
[15:00] <kenvandine> there was a unity8 crash during the test run, crash report at https://errors.ubuntu.com/oops/ef843348-19b5-11e5-be18-fa163e22e467
[15:27] <kenvandine> bingo... it has something to do with unity8
[15:28] <kenvandine> after it fails, if i restart unity8 without rebooting, i can run tests that use the osk and they pass
[15:28] <kenvandine> but if i run the full suite, it eventually blows up again
[15:39]  * kenvandine wonders why there is no "create bug" link on the oops page
[15:40] <jgdx> kenvandine, nice find!!
[15:40] <kenvandine> i just nailed down what needs a restart to get it into a working state again... not sure that's the actual cause...
[15:40] <kenvandine> but should be a good indicator
[15:41] <kenvandine> on the crashes page there is a create link to create a bug
[15:41] <kenvandine> but not on the oops pages
[15:41] <kenvandine> wtf!
[16:30] <jgdx> kenvandine, is it this one? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1467983
[16:31] <jgdx> nah
[16:31] <jgdx> did you file it?
[17:32] <kenvandine> jgdx, no... i tried to file it with ubuntu-bug, but it complains about missing fields in the crash file
[17:45] <kenvandine> jgdx, alesage: bug 1468029
[17:45] <alesage> kenvandine, thanks for that
[17:45] <kenvandine> alesage, i'm not really convinced it's unity8 at fault, but it is clearly part of it
[17:46] <alesage> kenvandine, ok interesting
[17:46] <kenvandine> and it affects more than just settings, it's been reported with webbrowser-app on vivid as well
[17:47] <kenvandine> unity8 has had landings for both wily and vivid overlay
[20:51] <jgdx> kenvandine, thanks!!