touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #00120
[Bug 1336671] Re: Intermittent mir_unit_tests.MesaDisplayTest.drm_device_change_event_triggers_handler test failure: libumockdev isn't thread safe
This bug was fixed in the package umockdev - 0.8.5-1
---------------
umockdev (0.8.5-1) unstable; urgency=medium
* New upstream release, to fix build and test on 32 bit architectures.
-- Martin Pitt <mpitt@xxxxxxxxxx> Fri, 11 Jul 2014 07:34:26 +0200
** Changed in: umockdev (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1336671
Title:
Intermittent
mir_unit_tests.MesaDisplayTest.drm_device_change_event_triggers_handler
test failure: libumockdev isn't thread safe
Status in Mir:
In Progress
Status in “umockdev” package in Ubuntu:
Fix Released
Bug description:
As seen in: http://s-jenkins.ubuntu-ci:8080/job/mir-clang-utopic-
amd64-build/799/console
To reproduce locally:
bzr branch lp:mir/devel mir-devel && cd mir-devel
mkdir build && cd build && cmake .. && make -j4
umockdev-wrapper bin/mir_unit_tests --gtest_filter=MesaDisplayTest.drm_device_change_event_triggers_handler --gtest_repeat=-1 --gtest_break_on_failure
(Ignore the segfault when the test fails, it's a side effect of
--gtest_break_on_failure)
Running with strace or on a system with high load increases the chances that we hit the problem. For example, running make -j4 in another mir branch while
running the tests does the trick for mir.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1336671/+subscriptions