cbmarcum commented on PR #289:
URL: https://github.com/apache/groovy-geb/pull/289#issuecomment-3448932601
After opening the PR #292 for this branch it reported an error in
`module/geb-junit5/src/test/groovy/geb/junit5/GebReportingTestReportingTest.groovy`.
After some investigation I found it wasn't caused by my test because when
testing the `bugfix/288-driver-cache` branch that test was randomly failing but
it did not fail in master after 20 test runs.
When testing 3 sets of 10 runs by: `:module:geb-junit5:test`
Failed run:
1,2,4,9
Succeeded run:
3,5,6,7,8,10
----
Failed run:
1,6,8,9,10
Succeeded run:
2,3,4,5,7
----
Failed run:
1,6,9
Succeeded run:
2,3,4,5,7,8,10
Almost always it was failing on
`reportsAreWrittenAtTheEndOfEachTestWhenConfigured` but occasionally it would
fail on `canWriteReportsWithTestDerivedName`.
From what I can tell it's not failing at the assertion. It's failing in the
runSuccessfuly method.
```
assert listener.wasExecutionSuccessful()
| |
| false
geb.junit5.fixture.TestExecutionResult@5bdc23a1
at
org.codehaus.groovy.runtime.InvokerHelper.createAssertError(InvokerHelper.java:414)
at geb.junit5.fixture.TestRunner.runSuccessfully(TestRunner.groovy:30)
at
org.codehaus.groovy.vmplugin.v8.IndyInterface.fromCache(IndyInterface.java:321)
at
geb.junit5.GebReportingTestReportingTest.runSuccessfully(GebReportingTestReportingTest.groovy:107)
at
org.codehaus.groovy.vmplugin.v8.IndyInterface.fromCache(IndyInterface.java:321)
at
geb.junit5.GebReportingTestReportingTest.reportsAreWrittenAtTheEndOfEachTestWhenConfigured(GebReportingTestReportingTest.groovy:55)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
```
Isolating just this test class runs just fine.
``:module:geb-junit5:test --tests "geb.junit5.GebReportingTestReportingTest"
No issues after 20 runs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
