Harden regression workflow dependency install#229
Merged
tshead2 merged 1 commit intosandialabs:mainfrom Mar 19, 2026
Merged
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
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
This hardens the regression test workflow after the recent PR exposed some fragility in the CI environment
setup.
The current workflow can fail during dependency installation because it installs system packages without
refreshing apt metadata, relies on some transitive Python dependencies for the documentation scenarios, and
always uploads the same artifact name across the test matrix.
Changes
actions/setup-pythonapt-get updatebefore installing system packagesffmpegandghostscriptwith-y --no-install-recommendspython -m pipconsistentlynbformatexplicitly, since the documentation regression step imports it directly.[all]install path for nowWhy
This is a workflow-only fix. It does not change Toyplot runtime behavior.
The goal is to make the regression job more reliable across the Python version matrix and reduce avoidable CI
failures caused by environment setup rather than code regressions.
Validation
This PR changes only
.github/workflows/regression-tests.yml.I verified the workflow diff locally with: