gnodet opened a new pull request, #27579: URL: https://github.com/apache/camel/pull/27579
## Motivation JUnit 6.x logs thousands of warnings when parallel test execution is enabled: > Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. This fires for all ~39 modules that have parallel execution enabled, producing noise in CI logs. ## Modifications Set `junit.jupiter.execution.parallel.config.executor-service=WORKER_THREAD_POOL` in the three places where JUnit parallel execution is configured: - `parent/pom.xml` — surefire `configurationParameters` block - `components/pom.xml` — failsafe `systemPropertyVariables` block - `core/camel-core/src/test/resources/junit-platform.properties` ## Result The warning is silenced and the `WORKER_THREAD_POOL` executor (a regular thread pool rather than a ForkJoinPool) is used for all parallel test runs. This also has the potential to improve test execution performance as noted in CAMEL-25260. **Note on `CamelParallelExecutionStrategy`**: this custom strategy continues to work correctly with `WORKER_THREAD_POOL`. It provides parallelism/pool-size configuration via the `ParallelExecutionConfiguration` interface. The `getSaturatePredicate()` method (a ForkJoinPool-specific monitoring hook that logged a warning on pool saturation) will no longer be called — this is acceptable as it was purely a logging/diagnostic callback. -- 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]
