Some jobs on https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck are taking longer than usual, are there any stuck pods?
Summary
https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1950/console contains timeout errors that occur after 15 hours. It normally only takes 12 hours to run the tests but we do have the jobs configured to timeout after 15 hours in case of system environmental issues or if something else goes wrong.
- Please check if https://ci.eclipse.org/jakartaee-tck has any stuck pods/resource packs/VM.
- Please restart our https://ci.eclipse.org/jakartaee-tck Jenkins just for good measure
- We will wait for a response on this ticket before running the same test again.
Steps to reproduce
Run https://ci.eclipse.org/jakartaee-tck/job/10/job/eftl-jakartaeetck-run-100, the last three times we ran this, we hit the timeout after running too long (15 hours).
What is the current bug behavior?
The Jenkins job times out because we hit the configured timeout. Since we have dedicated resource packs, we shouldn't ever time out (unless the overall system is running slower or there are stuck pods that aren't being utilized).
What is the expected correct behavior?
The tests should complete after 12 hours.
Relevant logs and/or screenshots
https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1950/console contains:
[runcts] OUT => [javatest.batch] Test not responding after 510,800 interrupts
[runcts] OUT => [javatest.batch] Test not responding after 510,900 interrupts
[runcts] OUT => [javatest.batch] Test com/sun/ts/tests/ejb30/lite/packaging/embed/provider/Client.java#customProvider_from_ejbembed has timed out and is not responding after 511,000 interrupts
[runcts] OUT => [javatest.batch] Test not responding after 511,000 interrupts
Cancelling nested steps due to timeout
Sending interrupt signal to process
Killing processes
kill finished with exit code 0
Sending interrupt signal to process
Killing processes
kill finished with exit code 1
script returned exit code 143
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] }
Failed in branch ejb30/lite/packaging
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (standalone-tck-build)
Stage "standalone-tck-build" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (standalone-tck-run)
Stage "standalone-tck-run" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
Exception: null
GitHub has been notified of this commit’s build result
Finished: ABORTED
REST API
Jenkins 2.332.3