-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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.
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
kv/kvserver: skip TestReplicaCircuitBreaker_Follower_QuorumLoss #76894
kv/kvserver: skip TestReplicaCircuitBreaker_Follower_QuorumLoss #76894
Conversation
Refs: cockroachdb#76781 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None
Can whoever stamps this bors it? I'm likely going to be offline until tomorrow. |
Yup, will do. |
bors r+ |
Sorry, had lots of stuff going on last night and totally forgot about this. |
Build failed: |
bors r+ |
Build failed: |
bors r+ |
Build failed: |
bors r+ |
Build failed: |
bors r+ It's getting comical |
To be honest it saddens me that skipping tests requires bors to re-run the full CI suite. There should be a way to override this when doing things like skipping tests. |
Build failed: |
bors r+ |
Build succeeded: |
Refs: #76781
Reason: flaky test
Generated by bin/skip-test.
Release justification: non-production code changes
Release note: None