| [jakartaee-tck-dev] Our Jenkins CI environment seems to be timing out while running the Platform TCK job... |
From https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1950/console:
"
[runcts] OUT => [javatest.batch] Test not responding after 458,400 interrupts [runcts] OUT => [javatest.batch] Test not responding after 458,500 interrupts [runcts] OUT => [javatest.batch] Test not responding after 458,600 interrupts [runcts] OUT => [javatest.batch] Test not responding after 458,700 interrupts [runcts] OUT => [javatest.batch] Test not responding after 458,800 interrupts [runcts] OUT => [javatest.batch] Test not responding after 458,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 459,000 interrupts [runcts] OUT => [javatest.batch] Test not responding after 459,000 interrupts [runcts] OUT => [javatest.batch] Test not responding after 459,100 interrupts [runcts] OUT => [javatest.batch] Test not responding after 459,200 interrupts [runcts] OUT => [javatest.batch] Test not responding after 459,300 interrupts [Pipeline] junit Recording test results [runcts] OUT => [javatest.batch] Test not responding after 459,400 interrupts [Checks API] No suitable checks publisher found. " I'll look around to see if I can find the statistics page for the Platform TCK (will add it to the wiki when I find it). Scott