You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per https://www.eclipse.org/lists/cu-dev/msg00563.html discussion thread, GlassFish 7 intermittently fails ManagedScheduledExecutorDefinitionTests.testScheduleWithCronTrigger TCK test. WildFly also fails the same.
This issue is for creating a pull request to back port ccded09 for a 3.0.1 release to address the TCK failure.
Error information copied from ^ email conversation:
From https://ci.eclipse.org/jakartaee-tck/job/10/job/jakarta-concurrency-tck-glassfish/138/consoleText:
"
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] ManagedScheduledExecutorDefinitionTests>Arquillian.run:138->testScheduleWithCronTrigger:147->TestClient.runTest:52->TestClient.runTest:60->TestClient.assertSuccessfulURLResponse:143->ArquillianTests.assertTrue:108 Output did not contain successful message: SUCCESS expected [true] but found [false]
[INFO]
[ERROR] Tests run: 148, Failures: 1, Errors: 0, Skipped: 0
"
The text was updated successfully, but these errors were encountered:
As per https://www.eclipse.org/lists/cu-dev/msg00563.html discussion thread, GlassFish 7 intermittently fails ManagedScheduledExecutorDefinitionTests.testScheduleWithCronTrigger TCK test. WildFly also fails the same.
This issue is for creating a pull request to back port ccded09 for a 3.0.1 release to address the TCK failure.
Error information copied from ^ email conversation:
The text was updated successfully, but these errors were encountered: