Integration tests pass consistently after configuring the `--max-workers=12` and by not setting the `testMaxParallelForks` (so it defaults to max-workers/4), except for one test[1] which is a test called ConcurrentTestRunnerTest to test the ConcurrentTestRunner.
This test is expected to fail when an atomic int is modified in parallel threads. This ensures ConcurrentTestRunner is running in parallel, but unfortunately, Github actions may be running with a single core (availableProcessors = 2). The logs are available in the summary section and saved for up to 5 days. Though the available processors are 2 and it seems the atomic int is never got executed in parallel. Any thoughts? @Dan Tagging you as you were the original author to little bit understand about this test. Available processors: 2 Available processors: 2 Available processors: 2 Available processors: 2 [1] https://github.com/apache/geode/actions/runs/4119919022 On Mon, 23 Jan 2023 at 11:05, Sai Boorlagadda <sai.boorlaga...@gmail.com> wrote: > After working through unit tests and the builds are passing. I am working > on adding an integration step to the build pipeline. > > Looks like there are a few (4 tests) failing[1] on the integration suite. > Let me know if anyone interested to look into them. It would really good to > get integration tests enabled on develop. > > Below 4 tests needs to be analyzed and fixed: > 1) LocatorLauncherJmxSerialFilterPropertyBlankIntegrationTest > > startDoesNotConfigureJmxSerialFilter_whenPropertyIsBlank_onJava8 > 2) LocatorLauncherGlobalSerialFilterPropertyEmptyIntegrationTest > > startDoesNotConfigureGlobalSerialFilter_whenPropertyIsEmpty > 3) VersionCommandJUnitTest > initializationError > 4) LoadClusterConfigFromDirInt > canStartWithDeployedJarInClusterConfig > > 1. https://github.com/apache/geode/actions/runs/3983609395/jobs/6829148633 > > Sai >