-
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/kvclient/kvcoord: TestTxnCoordSenderPipelining failed #68948
Comments
Ran 30k stress runs, can't reproduce. Worth a closer look though. |
kv/kvclient/kvcoord.TestTxnCoordSenderPipelining failed with artifacts on master @ 04a41e7915f4a89dcc1d0dbd92466c6adf79ec9f:
ReproduceTo reproduce, try: make stressrace TESTS=TestTxnCoordSenderPipelining PKG=./pkg/kv/kvclient/kvcoord TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1 Parameters in this failure:
Internal log
/cc @cockroachdb/kv nvanbenschoten |
I figured that may point at #67215 being a culprit for the recent flakiness, but the transactions in this test would have launched a heartbeat loop even before #67215. So this may hint at some slowdown in CI or some slowdown in something below this test that causes these transactions to block for up to a second. |
68834: bazel: build http docs w bazel r=rail a=rickystewart We generate this in a different way than the `Makefile` does -- we take all the proto descriptor sets (that we need to generate anyway as part of the build) and pass them in to `protoc` rather than passing a bunch of include paths, which wouldn't work terribly well in the sandbox. Also teach CI and `dev` to start building these docs. I deleted a stray comment in `pkg/server/serverpb/admin.proto` that was causing a diff in the generated file. I also had to patch `@com_github_pseudomuto_protoc_gen_doc` to quash a compiler error (I just deleted a dependency that isn't actually necessary). Closes #65814. Release note: None 69019: kv: deflake TestTxnCoordSenderPipelining r=nvanbenschoten a=nvanbenschoten Fixes #68948. This commit disables the transaction heartbeat loop in the test, which removes a dependency on timing. However, this doesn't explain why the test became slower over the past few days. We see in CI that on the two separate occasions where the test flaked, it took 1.08s and 1.41s, both above the 1s necessary for the test to flake. Co-authored-by: Ricky Stewart <[email protected]> Co-authored-by: Nathan VanBenschoten <[email protected]>
kv/kvclient/kvcoord.TestTxnCoordSenderPipelining failed with artifacts on master @ ed9411c488e93dca28a61a2abafc087aac00946e:
Reproduce
To reproduce, try:
Parameters in this failure:
Internal log
/cc @cockroachdb/kv nvanbenschoten
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: