test: set up itk nightly runs#1052
Open
kdziedzic70 wants to merge 1 commit intomainfrom
Open
Conversation
Contributor
There was a problem hiding this comment.
Code Review
This pull request refactors the ITK test execution by externalizing test scenarios into a JSON file and introducing a Python script to manage test history for nightly runs. The review feedback highlights critical improvements for error handling in the history processing script, specifically recommending that the script fail explicitly on network or file-loading errors to prevent data loss and ensure that the CI pipeline correctly identifies test failures through appropriate exit codes.
ace973a to
d942519
Compare
d942519 to
cb49919
Compare
cb49919 to
0961c8f
Compare
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.
Description
This PR:
nightly-metricsrolling release to be re-used for visual inspectionThank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
CONTRIBUTINGGuide.fix:which represents bug fixes, and correlates to a SemVer patch.feat:represents a new feature, and correlates to a SemVer minor.feat!:, orfix!:,refactor!:, etc., which represent a breaking change (indicated by the!) and will result in a SemVer major.bash scripts/format.shfrom the repository root to format)Fixes #<issue_number_goes_here> 🦕