In discovery, treat suite import failure similarly as build failure #743
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
pv
force-pushed
the
fix-discovery-importfail
branch
from
1f936de
to
a887747
Compare
Instead of giving up benchmark discovery on import failure, treat it similarly as build failures. Also try branch commits immediately if the first user-provided benchmark commit fails to work, and try rest of the commits only after those.
pv
force-pushed
the
fix-discovery-importfail
branch
from
a887747
to
e39f2b8
Compare
pv
added
the
backport-candidate
pv
removed
the
backport-candidate
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.
Instead of giving up benchmark discovery on import failure, treat it
similarly as build failures.
Also try branch commits immediately if the first user-provided benchmark
commit fails to work, and try rest of the commits only after those.