Repository navigation
test: shorten the slowest tests unless MPITEST_STRESS is set - #8047
Merged
Merged
Conversation
hzhou-muse
changed the title
Contributor
Author
|
test:mpich/ch3/most |
Contributor
Author
|
Test-time results on
The default cell's wall time went from 47m to 42m. The one failure, |
part/pingping now runs in run_mpitests and takes the DTP arguments through dtp_args, the same way as pt2pt/pingping. Previously it was the only DTP test still built as a standalone program. model: Opus 5.5
part/pingping sends at most 16 and pt2pt/pingping at most 256 messages per datatype, and both go back to 4096 when MPITEST_STRESS is set. Previously both always sent up to 4096 messages, which made them the two most expensive tests in a CI run. model: Opus 5.5
MPI_Comm_connect in both CH3 and CH4 now reads the default timeout from MPIR_CVAR_COMM_CONNECT_TIMEOUT, declared once in the device-neutral spawn code. The old MPIR_CVAR_CH3_COMM_CONNECT_TIMEOUT and MPIR_CVAR_CH4_COMM_CONNECT_TIMEOUT stay as alternate environment names. Previously each device declared its own copy of the same CVAR. model: Opus 5.5
…s set connect_timeout sets the default connect timeout to 3 seconds through MPI_T and uses 1 second in the info argument, and taskmanager and th_taskmanager spawn 16 tasks by default. With MPITEST_STRESS set they use the previous 20 and 5 second timeouts and 128 tasks. Previously the timeouts came from env= entries in the testlist, and these tests spent about 160 seconds of a CI run waiting. model: Opus 5.5
hzhou
force-pushed
the
pingping-stress
branch
from
October 22, 2026 21:29
30ad57d to
ac01a88
Compare
hzhou
approved these changes
Oct 22, 2026
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
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.
Pull Request Description
A few tests take a large share of a CI run's test time: in the ch4-ofi default cell, part/pingping and pt2pt/pingping take 224 s and 164 s of the 1916 s total, and connect_timeout and the taskmanager tests spend another ~160 s, mostly waiting on fixed timeouts or repeating the same work. part/pingping was also the only DTP test still built as a standalone program.
This PR makes the default runs of these tests short and keeps the previous load behind
MPITEST_STRESS:Additional changes:
dtp_args, the same way as pt2pt/pingping.MPIR_CVAR_CH3_COMM_CONNECT_TIMEOUTandMPIR_CVAR_CH4_COMM_CONNECT_TIMEOUTasMPIR_CVAR_COMM_CONNECT_TIMEOUT, with the old names kept as aliases, so connect_timeout can set it through MPI_T.Local runs:
Author Checklist
🤖 Generated with Claude Code