Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support bisecting from good commits to bad commits #597

Open
cushon opened this issue Jul 25, 2024 · 0 comments
Open

Support bisecting from good commits to bad commits #597

cushon opened this issue Jul 25, 2024 · 0 comments
Labels
help wanted Needs help from external contributors P2 We'll consider working on this in future. (Assignee optional) type: feature request New feature or request

Comments

@cushon
Copy link

cushon commented Jul 25, 2024

--bisect is very helpful for finding when a regression happened, but it doesn't seem to support bisecting from a bad commit to a good commit, i.e. to verify when a bug got fixed. This can be useful to understand when something in Bazel got fixed, and verify it was deliberate.
@fweikert fweikert added P2 We'll consider working on this in future. (Assignee optional) type: feature request New feature or request help wanted Needs help from external contributors labels Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Needs help from external contributors P2 We'll consider working on this in future. (Assignee optional) type: feature request New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cushon @fweikert