Failure in 'test_multiread'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
strongswan (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Builds without a source change now trigger the following:
Running suite 'watcher':
Running case 'read': +
Running case 'write': +
Running case 'multiread': -
Failure in 'test_multiread': timeout(14) (i = 0)
dumping 6 stack frame addresses:
/lib/
-> ??:?
/<<PKGBUILDDI
-> ??:0
/<<PKGBUILDDI
-> ??:0
/<<PKGBUILDDI
-> ??:0
/lib/
-> ??:?
/<<PKGBUILDDI
-> ??:0
Running case 'multiwrite': +
Passed 3/4 'watcher' test cases
This might be due to new toolchain or library versions.
I'll start an investigation of that.
Those builds used to be very reliable so far but recently started to "sometimes" break on:
Failure in 'test_multiread': timeout(14) (i = 0)
I started to work on that in bug 1794224 , but it has all the same symptoms than this issue here.
- showed up recently
- build time test timeout error
- not reproducible locally (too fast?)
Although it is not doing "much" disk I/O at the time I think I'll dup and track it together with bug 1794059