Skip to content

[MINOR] test use deterministic alphabetical test run order in surefire #2490

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Baunsgaard wants to merge 3 commits into from
+4 −0
Closed

[MINOR] test use deterministic alphabetical test run order in surefire #2490

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9856925
Use deterministic alphabetical test run order in surefire
Baunsgaard Jun 16, 2026
220e00e
Capture stacks of stalled surefire forks in test container
Baunsgaard Jun 16, 2026
bec5e70
Remove surefire fork watchdog from test container entrypoint
Baunsgaard Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -411,6 +411,10 @@
<!-- 1C means the number of threads times 1 possible maximum forks for testing-->
<forkCount>${test-forkCount}</forkCount>
<reuseForks>false</reuseForks>
<!-- Deterministic class ordering so a hang reproduces at the same
boundary across CI and local runs (default filesystem order
varies by machine, which hid the component-c fork hang). -->
<runOrder>alphabetical</runOrder>
<!-- Kill hung test forks before CI cancels the whole job. -->
<forkedProcessTimeoutInSeconds>${test-forkedProcessTimeout}</forkedProcessTimeoutInSeconds>
<!-- Force-kill forks that still have live threads after the test class completes. -->
Expand Down
Loading