-
Notifications
You must be signed in to change notification settings - Fork 133
ci: remove case_validator.py from ALWAYS_RUN_ALL #1330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
sbryngelson
merged 1 commit into
MFlowCode:master
from
sbryngelson:fix/remove-case-validator-always-run
Mar 20, 2026
+5
−3
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: MFlowCode/MFC
Length of output: 501
🏁 Script executed:
Repository: MFlowCode/MFC
Length of output: 1711
🏁 Script executed:
Repository: MFlowCode/MFC
Length of output: 897
🏁 Script executed:
Repository: MFlowCode/MFC
Length of output: 2963
🏁 Script executed:
Repository: MFlowCode/MFC
Length of output: 2292
🏁 Script executed:
Repository: MFlowCode/MFC
Length of output: 3382
🏁 Script executed:
Repository: MFlowCode/MFC
Length of output: 913
case_validator.py should not be excluded from ALWAYS_RUN_ALL
The comment on lines 47-48 claims validator changes only affect user-facing error messages, but input.py (lines 138-152) shows the validator is called during
generate()withvalidate_constraints(), which can raiseCaseConstraintErrorand fail test execution. Validator logic changes—not just error text—can cause tests to fail if they violate new or modified constraints.Removing case_validator.py from ALWAYS_RUN_ALL means validator-only changes won't trigger the full test suite, creating a blind spot for regressions. The proposed mitigation (keep validator-only changes in ALWAYS_RUN_ALL unless paired with actual source file changes) is appropriate.
Suggested fix
Also update the comment on line 47-48 to accurately describe validator behavior.