Fix wrapper test failures by running them sequentially #675
Conversation
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
The wrapper tests import multiple heavy external packages (PETSc, MINPACK, NLsolve, etc.) that can have issues with parallel initialization and resource contention. This change: 1. Forces sequential execution (nworkers=0) for wrapper tests specifically 2. Increases retry count from 3 to 5 for tests involving PETSc/MINPACK 3. Sets RETESTITEMS_NWORKERS=0 in CI workflow for wrapper group This should resolve the intermittent failures seen in: https://github.com/SciML/NonlinearSolve.jl/actions/runs/16865133167/job/47770956480 🤖 Generated with Claude Code Co-Authored-By: Claude <[email protected]>
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.
Summary
Problem
The wrapper tests import multiple heavy external packages (PETSc, MINPACK, NLsolve, SIAMFANLEquations, SpeedMapping, FixedPointAcceleration, FastLevenbergMarquardt, LeastSquaresOptim) that can have issues with parallel initialization and resource contention when multiple test workers try to load and initialize them simultaneously.
Solution
Force sequential execution (nworkers=0) for wrapper tests specifically:
test/runtests.jlto detect when GROUP=="wrappers" and set RETESTITEMS_NWORKERS=0Increased retry count from 3 to 5 for tests involving PETSc/MINPACK:
CI workflow configuration:
Test plan
🤖 Generated with Claude Code