SharedWakelock test unstable
Bug #1541854 reported by
Michał Sawicz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtmir (Ubuntu) |
Fix Released
|
High
|
Gerry Boland |
Bug Description
The SharedWakelock test is unstable, leading to FTBFS all to often:
https:/
Excerpts from the above:
[ RUN ] SharedWakelockT
unknown file: Failure
C++ exception with description "Process [python3] for service [com.canonical.
[ FAILED ] SharedWakelockT
[==========] 14 tests from 1 test case ran. (23928 ms total)
[ PASSED ] 13 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] SharedWakelockT
Related branches
lp:~gerboland/libqtdbustest/increase-wait-timeout
- Pete Woods (community): Approve
-
Diff: 34 lines (+16/-1)1 file modifiedsrc/libqtdbustest/QProcessDBusService.cpp (+16/-1)
Changed in qtmir: | |
assignee: | nobody → Gerry Boland (gerboland) |
status: | Triaged → In Progress |
affects: | qtmir → qtmir (Ubuntu) |
To post a comment you must log in.
Link points to a passing build.
That test was reliable on the old s-jenkins CI system, and hasn't changed in months. It's using dbusmock-qt5 in an uncontroversial way. No idea why it fails now. dbusmock-qt5 issue?