Mark same-commit failure boundary as flaky - #660
Merged
Conversation
When last_good and first_bad ran the same commit, a compare URL degenerates to X...X and misleads agents into commit bisection. Return no compare_url and note that the failure is likely flaky or environment-dependent instead. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
On production,
find_failure_originforTestGCCompact#test_moving_arrays_up_heapsreturnedlast_goodandfirst_badpointing at the same commit, and the compare URL degenerated to48ac726...48ac726. A self-compare URL misleads an agent into bisecting a commit range that does not exist, while the same-commit boundary is actually a strong signal that the failure is flaky or environment-dependent. When both boundary reports ran the same commit, omitcompare_urland return a note saying the failure is likely not caused by a code change.🤖 Generated with Claude Code