roachtest: skip scbench #76970
Merged
roachtest: skip scbench #76970
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
tbg
requested review from
a team and
srosenberg
and removed request for
a team
|
This change is |
See cockroachdb#56230. I don't usually go around skipping other team's tests, but this one regularly times out, occupying a cluster for 10h, and possibly contributing to timeouts of the roachtest suite as a whole. Looking at the failure issue it's also clear that the owning team is not deriving any signal whatsoever from this test at the moment. Release note: None
otan
approved these changes
Feb 24, 2022
|
bors r=otan ¡ǝʇɐɯ sʞuɐɥʇ |
|
Build succeeded: |
24 tasks
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.
See #56230.
I don't usually go around skipping other team's tests, but this one
regularly times out, occupying a cluster for 10h, and possibly
contributing to timeouts of the roachtest suite as a whole.
Looking at the failure issue it's also clear that the owning team is not
deriving any signal whatsoever from this test at the moment.
Release note: None