Skip to content

CI: add smoke test for spin bench - #161

Open
InessaPawson wants to merge 3 commits into
numpy:mainfrom
InessaPawson:spinbench-test
Open

InessaPawson wants to merge 3 commits into
numpy:mainfrom
InessaPawson:spinbench-test

Conversation

@InessaPawson

Copy link
Copy Markdown
Member

Follow-up to #159. Nothing in CI exercised spin bench, so a future incompatibility with spin or asv would go unnoticed. This adds a step after the test suite that registers the machine with asv and runs a single benchmark (Npv2D.time_broadcast) in dry-run mode.

I verified the step locally on macOS (Tahoe 26.5.2). I’d suggest checking the Windows/Linux runs as well.

@InessaPawson

Copy link
Copy Markdown
Member Author

According to CI, the smoke test passes on Linux and macOS, but Windows fails at asv machine --yes with exit code 1 and no output, likely due to how Git Bash resolves the asv entry point.

Should I push a diagnostic commit to check which asv and switch to python -m asv / python -m spin to bypass the .exe shim?

@InessaPawson
InessaPawson requested a review from seberg October 11, 2026 04:07
Comment thread .github/workflows/pythonpackage.yml Outdated
@InessaPawson
InessaPawson requested a review from seberg October 13, 2026 00:36
@seberg

seberg commented Oct 13, 2026

Copy link
Copy Markdown
Member

Hmmmmm, I am really not sure why the asv command fails on that that one (or two) windows job when it works on the 3.15 one?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants