You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2020/09/15 16:22:00 UTC
[jira] [Work started] (LOG4J2-2921) Enable parallel test execution
for compatible tests
[ https://issues.apache.org/jira/browse/LOG4J2-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on LOG4J2-2921 started by Matt Sicker.
-------------------------------------------
> Enable parallel test execution for compatible tests
> ---------------------------------------------------
>
> Key: LOG4J2-2921
> URL: https://issues.apache.org/jira/browse/LOG4J2-2921
> Project: Log4j 2
> Issue Type: Improvement
> Components: Build, Tests
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Priority: Major
>
> One area to improve the execution time of our builds is to [enable parallel test execution|https://junit.org/junit5/docs/current/user-guide/#writing-tests-parallel-execution] for all tests that can support that. Parallel tests are run in multiple threads on the same JVM rather than in forked JVMs (our current configuration). Thus, any tests that don't rely on JVM-global state (e.g., does not use environment variables, system properties, changing the default locale, shares an output file, etc.) should be able to support parallel test execution. Considering the amount of overhead introduced by JVM forks for every test, I'd hypothesize that this change could shave off at least 5-10 minutes from the total build time.
> Tests that cannot be run in parallel should be configured to run in their own phase using the existing forked-JVM settings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)