Add script for finding build regression using git bisect
#215
Conversation
This file contains 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
Blackhex
force-pushed
the
find-regression
branch
from
bee5d16
to
925362d
Compare
vejbomar
reviewed
Oct 22, 2024
Blackhex
force-pushed
the
find-regression
branch
2 times, most recently
from
e1b7270
to
ca0cc8e
Compare
vejbomar
approved these changes
Oct 22, 2024
Blackhex
force-pushed
the
find-regression
branch
from
ca0cc8e
to
092b46c
Compare
eukarpov
approved these changes
Oct 25, 2024
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.
So far this script is intended to be run manually:
with repository name as a single argument.
In the future, this can be extended to find regression in all the repositories (binutils, GCC, MinGW, Cygwin) and triggered automatically when daily updates workflow encounters build failure.