| Re: [jakartaee-tck-dev] Our Jenkins CI environment seems to be timing out while running the Platform TCK job... |
Created issue https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1655 to ask for help with the timeout running the Full Platform TCK tests.
Adding the Platform ml so they know that we are delayed in
getting Platform TCK results.
I found the page where we stored statistics previously but it only contains up to 2021 stats. I'll reach out to the Eclipse CI infrastructure people requesting that they check if they can see anything stuck and restart our Jenkins environment.
Scott
On 8/10/22 9:19 AM, Scott Marlow wrote:
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