GDBMultiNonStopRunControlTest.testSuspendProcessTwoThreadsRunning[gdbserver] is unstable #119
Labels
releng
Release engineering and project management
Comments
jonahgraham
changed the title
jonahgraham
added a commit
to jonahgraham/cdt
that referenced
this issue
Oct 27, 2022
The long sleep at the end of each thread is to make sure that while the test code is waiting for an event the "other" thread doesn't finish. 3 seconds is not long enough for this. This is similar to why we need dsf.gdb.tests.timeout.multiplier for other tests. Especially on the build machines the tests can run much slower causing the sleep to be insufficient. Increasing this to 30 seconds doesn't make the test suites take any longer, when they are all passing. Fixes eclipse-cdt#119
jonahgraham
added a commit
that referenced
this issue
Oct 28, 2022
The long sleep at the end of each thread is to make sure that while the test code is waiting for an event the "other" thread doesn't finish. 3 seconds is not long enough for this. This is similar to why we need dsf.gdb.tests.timeout.multiplier for other tests. Especially on the build machines the tests can run much slower causing the sleep to be insufficient. Increasing this to 30 seconds doesn't make the test suites take any longer, when they are all passing. Fixes #119
|
It failed again on Jenkins I think this is because although I increased the time the process would stay alive for, I also need to increase how long to wait for. |
jonahgraham
added a commit
to jonahgraham/cdt
that referenced
this issue
Nov 9, 2022
jonahgraham
added a commit
that referenced
this issue
Nov 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This test regularly fails on Jenkins with this error:
Error Message
Timed out waiting for ServiceEvent: org.eclipse.cdt.dsf.mi.service.command.events.MIStoppedEvent
Stacktrace
Standard Output
168,523 "testSuspendProcessTwoThreadsRunning[gdbserver]" requesting gdb with gdbserver. Launched gdb 8.1.1.
The text was updated successfully, but these errors were encountered: