Maven surefire.rerunFailingTestsCount option does not work in the case where there are test profiles or resources, unless the test order falls such that the failing test uses the last profile/resource

[holly-cummins]

This is a future issue, which will be created by #34681. Raising this for tracking and discussion.

[quarkus-bot]

/cc @quarkusio/devtools (maven)

[gsmet]

The test is not rerun immediately after the failing one?

[holly-cummins]

The test is not rerun immediately after the failing one?

Oh, sorry, I created an issue in haste to have something to anchor to, but I should have added context. Re-running is working fine in main, but it's broken by #34681. The problem is that the quarkus test extension shuts down the classloaders and app when switching between resources, so that by the time maven triggers the rerun, it's trying to run against a terminated app.

When maven triggers the re-run, discovery is re-executed, but not classloading, so we don't get a chance to make a 'fresh' app.

[holly-cummins]

I accidentally confirmed by doing #46945 that this is now fixed in my branch. Hurray! So I'm going to close as fixed, and assume that #46945 will protect against future regressions.