=== pitti_ is now known as pitti === pitti is now known as Guest21493 === Guest21493 is now known as pitti_ === pitti_ is now known as pitti [05:56] 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] ah, so that's the latest news? [05:58] eg. not trying to set up $something_else for flavors? [05:58] or is jenkins an app name?:) [05:59] jenkins is a build server software [05:59] morning knome :) [05:59] yup, that seems to be the state of things [06:00] mmhm === boiko_ is now known as boiko [14:12] alesage, not sure that's the same bug [14:12] alesage, i'm seeing it on mako [14:12] alesage, oSoMoN saw the same problem yesterday on krillin with vivid [14:12] alesage, for the webbrowser-app [14:20] 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] hey jgdx [14:22] hey kenvandine [14:22] oSoMoN, what is bugging me is that it gets the system in a bad state [14:22] i can't even run a single test that uses keyboard.write after it fails the first time [14:22] but manual use of the osk works fine [14:22] but nothing with autopilot that uses the osk works [14:23] kenvandine, you're in that state now? [14:23] yes [14:23] definitely sounds like an issue in autopilot itself [14:23] i don't think so [14:23] since it persists across autopilot runs [14:23] until reboot [14:23] do we have any autopilot expert around that could help investigate the issue? [14:24] alesage, suggested talking to veebers, but he's not around right now [14:25] oh wait... somethings crashing [14:25] but not leaving .crash files [14:27] apport-noui-_var_crash__usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_socket-demangler.32011.crash.log [14:27] maybe it is mir related [14:27] 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] would help to know what's between autopilot and the osk :) [14:33] kenvandine, oSoMoN I'm listening--if it's a mir thing racarr was helping before [15:00] there was a unity8 crash during the test run, crash report at https://errors.ubuntu.com/oops/ef843348-19b5-11e5-be18-fa163e22e467 [15:27] bingo... it has something to do with unity8 [15:28] after it fails, if i restart unity8 without rebooting, i can run tests that use the osk and they pass [15:28] 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] kenvandine, nice find!! [15:40] 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] but should be a good indicator [15:41] on the crashes page there is a create link to create a bug [15:41] but not on the oops pages [15:41] wtf! [16:30] kenvandine, is it this one? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1467983 [16:30] Launchpad bug 1467983 in unity8 (Ubuntu) "/usr/bin/unity8-dash:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:~QString:UbuntuMirClientIntegrationPlugin::create" [Undecided,Confirmed] [16:31] nah [16:31] did you file it? === pgraner is now known as pgraner-afk [17:32] jgdx, no... i tried to file it with ubuntu-bug, but it complains about missing fields in the crash file [17:45] jgdx, alesage: bug 1468029 [17:45] bug 1468029 in unity8 (Ubuntu) "unity8 crash breaking autopilot tests entering text with OSK" [Undecided,New] https://launchpad.net/bugs/1468029 [17:45] kenvandine, thanks for that [17:45] alesage, i'm not really convinced it's unity8 at fault, but it is clearly part of it [17:46] kenvandine, ok interesting [17:46] and it affects more than just settings, it's been reported with webbrowser-app on vivid as well [17:47] unity8 has had landings for both wily and vivid overlay === pgraner-afk is now known as pgraner [20:51] kenvandine, thanks!!