Exclude Redis dev mode tests in dev mode to avoid classloading chaos

[holly-cummins]

As suggested by @ozangunalp.

Avoids these errors:

2025-06-10 15:05:09,508 ERROR [io.qua.test] (Test runner thread) >>>>>>>>>>>>>>>>>>>> Summary: <<<<<<<<<<<<<<<<<<<<
testContinuousTestingReusesInstanceWhenPropertiesAreNotChanged() class io.quarkus.test.config.TestConfigProviderResolver cannot be cast to class io.quarkus.test.config.TestConfigProviderResolver (io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @24af801f; io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @46b15282)
DevServicesRedisContinuousTestingTest class io.quarkus.test.config.TestConfigProviderResolver cannot be cast to class io.quarkus.test.config.TestConfigProviderResolver (io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @24af801f; io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @46b15282)
testDevModeServiceDoesNotRestartContainersOnCodeChange() class io.quarkus.test.config.TestConfigProviderResolver cannot be cast to class io.quarkus.test.config.TestConfigProviderResolver (io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @24af801f; io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @46b15282)
testContinuousTestingDisablesDevServicesWhenPropertiesChange() class io.quarkus.test.config.TestConfigProviderResolver cannot be cast to class io.quarkus.test.config.TestConfigProviderResolver (io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @24af801f; io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @46b15282)
testContinuousTestingCreatesANewInstanceWhenPropertiesAreChanged() class io.quarkus.test.config.TestConfigProviderResolver cannot be cast to class io.quarkus.test.config.TestConfigProviderResolver (io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @24af801f; io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @46b15282)
testDevModeServiceUpdatesContainersOnConfigChange() class io.quarkus.test.config.TestConfigProviderResolver cannot be cast to class io.quarkus.test.config.TestConfigProviderResolver (io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @24af801f; io.quarkus.test.config.TestConfigProviderResolver is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @46b15282)

The errors aren't great, and ideally we'd fix them, but running continuous testing tests in continuous testing mode isn't something we'd normally expect to be able to do.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit ad52ba5.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[gsmet]

But don't you exclude them already from the Surefire run:

quarkus/integration-tests/redis-devservices/pom.xml

Lines 139 to 160 in ad52ba5

	<execution>
	<id>default-test</id>
	<goals>
	<goal>test</goal>
	</goals>
	<configuration>
	<excludes>
	<exclude>**/continuoustesting/**/*.java</exclude>
	</excludes>
	</configuration>
	</execution>
	<execution>
	<id>devmode-test</id>
	<goals>
	<goal>test</goal>
	</goals>
	<configuration>
	<includes>
	<include>**/continuoustesting/**/*.java</include>
	</includes>
	</configuration>
	</execution>

[holly-cummins]

Yes, the maven side is working fine. The scenario being supported here is running the tests directly in dev mode; that is, cd integration-tests/redis-devservices; mvn quarkus:dev. It turns out that this is useful to do because this drives dev mode and continuous testing harder than the dev mode and continuous tests do, and can find some defects/help debug issues.

[gsmet]

OK, thanks for the explanation!

[holly-cummins]

Ideally things would work even without the exclude, but continuous-testing-in-continuous-testing is a pretty high bar. 😵‍💫