Repository navigation
fix(decisions): a later run that covers a failure's files closes it (0.24.1) - #61
Merged
Merged
Conversation
…0.24.1) A failing run naming test files, followed by a passing run of the same runner over the whole suite, the same files, or a folder holding them, reads "failed, then passed". The broader pass was keyed differently and only suppressed the failure, so the row vanished. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PR brief: 2 agent commits · 8 of 25 test files reach this diffRun at least these. Selection is a safe superset; it never marks a test safe to skip.
What each commit did
Claims checked
What each changed file reaches
Paths above are under Tests to run (8)
Blast radius by changed file: 24 dependents
blastline 0.24.1. Selection is advisory unless your workflow gates on it. How selection works. Graph |
Review of #61: a pass covers everything only with no argument but flags that report, time or schedule; any selecting flag or bare name narrows it to nothing, also under the same key. Paths count only from the same cd as the failure, by equality or folder prefix. A pass in the same record keeps a failure from being called its last run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
taylorg009
marked this pull request as ready for review
October 22, 2026 02:54
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.
Why
On a real web-app PR, the agent's new tests failed in two runs that named the files, then passed in a run over their folder. Blastline 0.24.0 keyed the broader run differently, so it only stopped the failures from being called the last word, and How this PR was decided came out empty.
What changes
decisionsInkeeps every passing run with its targets. A failure is reported as "failed, then passed" when it's followed by a passing run of the same runner that covers its files: the whole suite (no targets), the same files, or a folder holding them. A later pass on unrelated files still closes nothing and keeps the failure from being called the last word, as before.Evidence
1 failed | 56 passed), then passed in a later run that named it (104 passed).🤖 Generated with Claude Code