Aurélien Pupier created CAMEL-25260:
---------------------------------------
Summary: Try
junit.jupiter.execution.parallel.config.executor-service=WORKER_THREAD_POOL
Key: CAMEL-25260
URL: https://issues.apache.org/jira/browse/CAMEL-25260
Project: Camel
Issue Type: Test
Components: build system
Affects Versions: 4.23.0
Reporter: Aurélien Pupier
in logs, there are many times:
{noformat}
[INFO] 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.
{noformat}
could be worthy to give a try to see if there are improvements (maybe also with
the other work in progress with -T1C)
either it is better and use it, or not better and set
junit.jupiter.execution.parallel.config.executor-service=FORK_JOIN_POOL to
avoid the thousands of messages in the log
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
