Run Slurm script unit tests in CI#2744
Merged
Merged
Conversation
This was referenced Jul 15, 2026
fabrizio2210
marked this pull request as ready for review
July 15, 2026 13:04
asteny
approved these changes
Jul 16, 2026
This was referenced Jul 16, 2026
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
test-pythonMakefile target using Python unittest discovery*_test.pysuites in all the repoci-successdependency setWhy
This extracts the reusable unit-test runner from #2719 into a standalone change based on
main. Keeping the runner independent lets Python tests in #2719, #2742, #2743, and future pull requests use the same CI job without depending on a health-check behavior change.The discovery root cover all the Python scripts. In particular, this ensures #2743 runs its
check_runner_test.pyandwrite_soperator_metadata_test.pysuites, as well as the existing worker tests.PR #2743 is stacked on this branch so its checked-out head contains the Make target; #2742 remains stacked on #2743. Because the repository uses
pull_request_target, the new job becomes available after this PR merges intomain. Synchronizing #2743 after that merge will trigger the 109-test suite.Validation
env PYTHONDONTWRITEBYTECODE=1 make test-pythonon this branch: 102 tests passed.github/workflows/one_job.ymlwith PyYAMLgit diff --check origin/main...HEAD