Skip to content

perf(ci): parallelize the clean-state suite too #46

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

Merged
ManSio merged 1 commit into from
Sep 26, 2026
Merged

perf(ci): parallelize the clean-state suite too #46

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 7 additions & 2 deletions scripts/verify_clean_state.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,8 +133,13 @@ else
|| { echo -e "${RED}PIP INSTALL FAILED${NC}"; exit 1; }
fi

echo "Running full test suite (no filters)..."
RESULT=$("$VENV_BIN/python" -m pytest tests/ -q --tb=short 2>&1)
echo "Running full test suite (no filters, parallel)..."
# -n auto (pytest-xdist, dev dep): SAME selection as before — no file list, and
# pyproject addopts keep `-m 'not slow and not benchmark'` — only spread across
# cores. This is exactly the set the `test` job runs (and which passed in
# parallel on ubuntu+windows), so parallel safety is already proven. Measured
# locally: 197s -> 71s (12 cores); CI runners have 4 cores. No quality loss.
RESULT=$("$VENV_BIN/python" -m pytest tests/ -q --tb=short -n auto 2>&1)
EXIT_CODE=$?

PASSED=$(echo "$RESULT" | grep -oE '[0-9]+ passed' | head -1 | grep -oE '[0-9]+' || echo "0")
Expand Down
Loading