** Description changed: - This is the current crash of the dialer-app tests from - http://ci.ubuntu.com/smokeng/trusty/touch/mako/76:20131219:20131218.2/5557 - /dialer-app-autopilot/ + In autopilot tests, sometimes clients fail to start (crash) causing the test to fail. Considering an example test output: + https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/ + the unity8 log file: + https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/artifact/results/log/unity8.log + does not contain a "REJECT" string - which would indicate unity-mir/unity8 rejects the client connection. So the connection is failing for another reason. + + However the log file indicates there are many unity8/mir crashes, + eventually breaking things to be unrecoverable. The bad crashes appears + to be: + + terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >' + what(): error during hwc set() + + and then on next invocation: + + terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >' + what(): compositor_acquire would block; probably too many clients. + + From here on, Mir fails to restart at all. Then all AP test fail, as + clients (rightly) fail to start (they shouldn't crash though, a nice + error message would be better). + + + Note that AP reboots the device after each test suite, hence you see + multiple invocations of unity8/mir in the unity8.log file - that's + normal. + + + We need a more reliable way to reproduce this problem. Working on it (gerry)... + + + ============================ old description of bug ===================================== + This is the current crash of the dialer-app tests from http://ci.ubuntu.com/smokeng/trusty/touch/mako/76:20131219:20131218.2/5557/dialer-app-autopilot/ ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: dialer-app 0.1+14.04.20131209-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l Architecture: armhf CurrentDesktop: Unity Date: Thu Dec 19 05:33:28 2013 ExecutablePath: /usr/bin/dialer-app ExecutableTimestamp: 1386563099 ProcCmdline: dialer-app ProcCwd: /home/phablet Signal: 6 SourcePackage: dialer-app StacktraceTop: - ?? () from /lib/arm-linux-gnueabihf/libc.so.6 - raise () from /lib/arm-linux-gnueabihf/libc.so.6 - abort () from /lib/arm-linux-gnueabihf/libc.so.6 - QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 - ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqubuntumirclient.so + ?? () from /lib/arm-linux-gnueabihf/libc.so.6 + raise () from /lib/arm-linux-gnueabihf/libc.so.6 + abort () from /lib/arm-linux-gnueabihf/libc.so.6 + QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 + ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqubuntumirclient.so UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262982 Title: Random mir failures running unity8 shell during AP tests To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1262982/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
