FIX-292: Reuse eight test workers and avoid repeated build phases - #360
Draft
peter-lawrey wants to merge 3 commits into
Draft
peter-lawrey wants to merge 3 commits into
peter-lawrey wants to merge 3 commits into
Conversation
peter-lawrey
changed the title
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Run eligible tests in up to eight reused worker JVMs, with a serial/fresh fallback and unchanged discovery, assertions, failure policy and dependencies. 23 classes use the ordinary pool. Three classes remain serial/fresh: BlockingEventLoopShutdownTest after an observed reverse-order shutdown warning, and LongPauserTest plus YieldingPauserTest after timing assertions failed on both Zing 8 and 11. The final split is checked in both class orders; isolation does not diagnose or repair the underlying failures.
Use non-forking source-JAR goals at package so Maven does not repeat earlier lifecycle phases. Preserve the existing main/test source classifiers, plugin versions and normal validation checks. Production and test sources are unchanged.
Validation on Linux/OpenJDK 21 with a pinned private Maven cache: clean verify and the CI named-goal route both retain all 248 cases, including 1 existing skips, with no failures, errors or reruns in the final qualified runs. Case identities and execution partitions match the original suite; actual worker processes/reuse are recorded. Runtime, resource and source archive contents are unchanged, apart from embedded POM metadata and generated timestamps.
-Ptest-serialretains full serial/fresh coverage. Explicit-Dtestand baresurefire:testremain conservative debug routes. TeamCity draft #175 wires the named executions into a manual branch pilot and provides matched four/eight-worker controls; the old bare-Surefire Build-All step does not activate this split. A whole-CI speedup is not yet measured.These are local qualification results. New-head CI and platform results remain review gates; previous-head failures are not treated as fixed by this configuration change.
The Zing failures are recorded in Java 11 build 1365949 and Java 8 build 1365950. The three-class split preserves the complete suite locally; new platform results are still required.