Refactor pytest GitHub Actions workflow#448
Merged
BrianJKoopman merged 8 commits intomainfrom Mar 20, 2026
Merged
Conversation
BrianJKoopman
added a commit
to simonsobs/socs
that referenced
this pull request
Apr 7, 2026
These changes were all based on those made in [1]. [1] - simonsobs/ocs#448
BrianJKoopman
added a commit
to simonsobs/socs
that referenced
this pull request
Apr 7, 2026
These changes were all based on those made in [1]. [1] - simonsobs/ocs#448
BrianJKoopman
added a commit
to simonsobs/socs
that referenced
this pull request
Apr 7, 2026
These changes were all based on those made in [1]. [1] - simonsobs/ocs#448
6 tasks
BrianJKoopman
added a commit
to simonsobs/socs
that referenced
this pull request
Apr 7, 2026
* Replace cancel-workflow-action with concurrency * Refactor pytest Actions workflow These changes were all based on those made in [1]. [1] - simonsobs/ocs#448 * Drop testing for 3.12 This is broken for the way we install in the workflow, but should still work if sotodlib is pip installed separately. * Drop support for Python 3.7 * Set appropriate timeouts * Group integ tests to run in parallel jobs * Updated skipped-pytest workflow
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
1 participant
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.
Description
This PR refactors the pytest workflow in order to run the unit tests on all supported Python versions (3.7-3.12). It also now runs the integration tests in parallel with the unit tests, and uploads the merged coverage report in a separate job.
I debated whether to run the integration tests after the unit tests pass, or in parallel, and figured parallel at least finishes the CI run slightly faster, even if we end up running the integration tests times that unit tests fail early. Thoughts on this welcome.
EDIT: We'll probably need to change the configured expected checks. I'll handle that once things settle. This also means I need to update the
skipped-pytest.ymlworkflow, but haven't yet.Motivation and Context
I've been thinking about doing this for a while. It'd be especially useful to check things work across versions if we ever end up implementing #405.
Uploading the coverage report in a separate job allows the upload job to fail and be retried without needing to re-run the tests again.
How Has This Been Tested?
I tested the workflow with an
on: pushbefore submitting this PR.Types of changes
Checklist: