Follow-up of #792 (item 3 of its Proposed fixes), deliberately left out of #795.
rerunFailingTestsCount=3 is configured for the precommit profile
(opendj-server-legacy/pom.xml:1284), yet the failing run analysed in #792 has no Flakes:
section in its report and the build failed on the first occurrence: the rerun did not trigger
for AssuredReplicationServerTest.testSafeDataFromRS, a TestNG @DataProvider driven method
(it failed on invocation 26 of 360).
What to do
- Confirm on a deliberately flaky
@DataProvider driven test whether failsafe/TestNG reruns it
at all.
- If it is the known surefire/TestNG data-provider limitation, decide whether we keep relying
on the setting for the replication suites, or drop it so that every failure is treated as
real.
Either way the answer should be written down: the current setting reads as a safety net which
may not exist for exactly the tests which need it most.
Follow-up of #792 (item 3 of its Proposed fixes), deliberately left out of #795.
rerunFailingTestsCount=3is configured for theprecommitprofile(
opendj-server-legacy/pom.xml:1284), yet the failing run analysed in #792 has noFlakes:section in its report and the build failed on the first occurrence: the rerun did not trigger
for
AssuredReplicationServerTest.testSafeDataFromRS, a TestNG@DataProviderdriven method(it failed on invocation 26 of 360).
What to do
@DataProviderdriven test whether failsafe/TestNG reruns itat all.
on the setting for the replication suites, or drop it so that every failure is treated as
real.
Either way the answer should be written down: the current setting reads as a safety net which
may not exist for exactly the tests which need it most.