| Re: [jakartaee-platform-dev] Renamed to possible GlassFish 7 regression related to ejb30/lite/packaging/embed/provider tests timing out... |
Adding the GlassFish team as https://github.com/eclipse-ee4j/jakartaee-tck/issues/1110 seems to be recreating for me locally (will know for sure when the test times out).
As mentioned in issue/1110, each tests appears to be timing out
for me locally just like in Jenkins. Will probably take a few
hours for my local test to complete.
These failures first started on Saturday but since we don't do daily TCK runs, I'm not sure of when the problem started other than the previous July 31 weekend GlassFish TCK testing didn't have this problem.
Scott
On 8/10/22 3:30 PM, Scott Marlow wrote:
It turns out that the "Test not responding after" message comes from the Java Test Harness. I created https://github.com/eclipse-ee4j/jakartaee-tck/issues/1110 for tracking the timeout issue. I'll try to recreate locally.
Scott
On 8/10/22 10:01 AM, Scott Marlow wrote:
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.
On 8/10/22 9:29 AM, Scott Marlow wrote:
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