[regression] [testsfail] failure in CI on SimpleDispatchThreadTest.keeps_dispatching_after_signal_interruption
Bug #1441620 reported by
Kevin DuBois
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Alexandros Frantzis | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
11: [ FAILED ] SimpleDispatchT
failed on CI on a branch that was just modifying the demo code.
https:/
Related branches
lp://staging/~afrantzis/mir/fix-1441620-simple-dispatch-thread-self-destruction-test
Rejected
for merging
into
lp://staging/mir
- Chris Halse Rogers: Needs Information
- Kevin DuBois (community): Approve
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Alan Griffiths: Approve
- Alberto Aguirre (community): Approve
-
Diff: 80 lines (+22/-1)3 files modifiedinclude/common/mir/dispatch/simple_dispatch_thread.h (+4/-0)
src/common/dispatch/simple_dispatch_thread.cpp (+11/-1)
tests/unit-tests/dispatch/test_simple_dispatch_thread.cpp (+7/-0)
lp://staging/~raof/mir/remove-eventloop-self-immolation
- Alan Griffiths: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 96 lines (+29/-28)2 files modifiedsrc/common/dispatch/simple_dispatch_thread.cpp (+8/-2)
tests/unit-tests/dispatch/test_simple_dispatch_thread.cpp (+21/-26)
Changed in mir: | |
assignee: | nobody → Alexandros Frantzis (afrantzis) |
Changed in mir: | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in mir: | |
milestone: | none → 0.13.0 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The problem is actually in the previous test: SimpleDispatchT hreadTest. handles_ destruction_ from_dispatch_ callback
From the valgrind trace in CI output:
... hreadTest_ handles_ destruction_ from_dispatch_ callback_ Test::TestBody( ) (test_simple_ dispatch_ thread. cpp:214)
by 0x13997A3: SimpleDispatchT
...
SimpleDispatchT hreadTest. keeps_dispatchi ng_after_ signal_ interruption fails because it forks a process which when finished reports all valgrind errors, even if they were caught in the parent process.