tests/manual: trim saved state in coreos-builds-bisect.py #3381
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
The statefile that tracks the progress of a bisect will today have all the builds from a given stream in it when really it only needs to keep track of the range of builds between the known good and known bad entries. Let's trim it to just that range of builds.
dustymabe
force-pushed
the
dusty-bisect-script
branch
from
701a2cc to
24357f4
Compare
dustymabe
changed the title
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.
The statefile that tracks the progress of a bisect will today have all the builds from a given stream in it when really it only needs to keep track of the range of builds between the known good and known bad entries. Let's trim it to just that range of builds.