Include detailed bisect log with file paths #363
Merged
Conversation
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
gregdodd
changed the title
gregdodd
force-pushed
the
09-08-include_detailed_bisect_log_with_file_paths
branch
from
6d4e3b0 to
18b7182
Compare
gregdodd
force-pushed
the
09-08-include_detailed_bisect_log_with_file_paths
branch
from
18b7182 to
56973df
Compare
nikita8
approved these changes
Sep 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
TL;DR
Add source location information to test cases and enhance bisect logging with file paths and line numbers.
What changed?
source_locationmethod to Minitest test cases that returns the file path and line number where the test is definedlog/bisect_test_details.log) that includes file paths and line numbers for each test in the failing order