fix: check command before running analyze - #50
Merged
Conversation
Owner
|
Sorry for the delay, not sure why I did not receive the notification about it. |
brunoerg
approved these changes
Jul 20, 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.
fixes: #44
We check the command before running analyze
Previously: A bad command (e.g. an invalid --run_test filter, which makes Boost exit 200) failed for every mutant. Each failure was recorded as killed, so the run reported a
incorrect 100% mutation score.
Now: The run aborts immediately with a clear error, no mutants are analyzed (they stay pending), and the process exits non-zero.