foo/bar: TestFormatter failed #2
Comments
|
storage.TestReplicateQueueRebalance failed on release-0.1 @ abcd123: Help
See also: How To Investigate a Go Test Failure (internal) Same failure on other branches
|
|
foo/bar.TestFormatter failed on release-19.2 @ deadbeef: Help
See also: How To Investigate a Go Test Failure (internal) |
renatolabs
pushed a commit
that referenced
this issue
Jul 12, 2023
106502: batcheval: delete flaky integration test r=aliher1911 a=aliher1911 TestLeaseCommandLearnerReplica is fundamentally flaky as commit can't retry all underlying replication failures and acceptable failure causes are not exposed on the higher levels where test operates. What test is supposed to verify that failures to propose with invalid lease are not causing pipelined writes to fail but are retried. More details described in original PR cockroachdb#35261 where this test is introduced. In absence of direct controls of that, test is trying to move leases between replicas, but this action could cause different failures to happen which can't be filtered out. For example: `failed to repropose 0b9a11f4bef0e3d3 at idx 16 with new lease index: [NotLeaseHolderError] ‹reproposal failed due to closed timestamp›` and `stale proposal: command was proposed under lease #2 but is being applied under lease: ...` While closed timestamp could be mitigated by changing settings, second one is opaque to the caller and hard to filter out. Release note: None Fixes cockroachdb#104716 Co-authored-by: Oleg Afanasyev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
foo/bar.TestFormatter failed on release-19.2 @ deadbeef:
Help
Parameters:
GOFLAGS=-race_test,ROACHTEST_cloud=test,ROACHTEST_cpu=2This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: