-
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: TestReplicaCircuitBreaker_RangeFeed failed #76856
Labels
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
Comments
cockroach-teamcity
added
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
labels
Feb 21, 2022
tbg
added a commit
to tbg/cockroach
that referenced
this issue
Feb 24, 2022
Refs: cockroachdb#76856 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None
maryliag
pushed a commit
to maryliag/cockroach
that referenced
this issue
Feb 28, 2022
Refs: cockroachdb#76856 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None
RajivTS
pushed a commit
to RajivTS/cockroach
that referenced
this issue
Mar 6, 2022
Refs: cockroachdb#76856 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None
craig bot
pushed a commit
that referenced
this issue
Mar 28, 2022
78241: kvserver: de-flake TestReplicaCircuitBreaker_RangeFeed r=erikgrinaker a=tbg Fixes #76856. Release note: None 78312: roachtest: improve debugging in transfer-leases r=erikgrinaker a=tbg This test failed once and we weren't able to figure out why; having the range status used by the test would've been useful. Now this is saved and so the next time it fails we'll have more to look at. Closes #75438. Release note: None 78422: roachtest: bump max wh for weekly tpccbench/nodes=12/cpu=16 r=srosenberg a=tbg [It was maxing out, reliably.](https://roachperf.crdb.dev/?filter=&view=tpccbench%2Fnodes%3D12%2Fcpu%3D16&tab=gce) Release note: None 78490: sqlproxyccl: exit pod-watcher-client on local context cancellation r=jaylim-crl,darinpp a=stevendanna Previously, we used grpcutil.IsContextCanceled to detect when a returned gRPC error was the result of a context cancellation. I believe that the intent of this code was to detect when the _local_ context was cancelled, indicating that we are shutting down and thus the watch-pods-client goroutine should exit. This works because the gRPC library converts a local context.Canceled error into a gRPC error. And, in gRPC before 1.45, if a server handler returned context.Canceled, the returned gRPC error would have status.Unknown, and thus not trigger this exit behavior. As of gRPC 1.45, however, a context.Canceled error returned by a server handler will also result in a gRPC error with status.Canceled [0], meaning that the previous code will force the goroutine to exit in response to a server-side error. From my reading of this code, it appears we want to retry all server-side errors. To account for this, we now only break out of the retry loop if our local context is done. Further, I've changed the test directory server implementation to return an arguably more appropriate error when it is shutting down. Fixes #78197 Release note: None Co-authored-by: Tobias Grieger <tobias.b.grieger@gmail.com> Co-authored-by: Steven Danna <danna@cockroachlabs.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
kv/kvserver.TestReplicaCircuitBreaker_RangeFeed failed with artifacts on master @ 1a89121d67fa02d5c674766ea01d3c78455fd28b:
Help
See also: How To Investigate a Go Test Failure (internal)
Parameters in this failure:
This test on roachdash | Improve this report!
Jira issue: CRDB-13304
The text was updated successfully, but these errors were encountered: