cockroachdb / cockroach

CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
https://www.cockroachlabs.com
Other
29.87k stars 3.77k forks source link

roachtest: transfer-leases/signal failed #85203

Closed cockroach-teamcity closed 1 year ago

cockroach-teamcity commented 2 years ago

roachtest.transfer-leases/signal failed with artifacts on release-22.1 @ 7d74b25b21bdabc3b0cc87ced447acc9967eb4d5:

The test failed on branch=release-22.1, cloud=gce:
test artifacts and logs in: /artifacts/transfer-leases/signal/run_1
    quit.go:70,quit.go:317,soon.go:71,retry.go:207,soon.go:77,soon.go:49,quit.go:226,quit.go:93,quit.go:152,context.go:91,quit.go:151,quit.go:93,quit.go:52,quit.go:353,test_runner.go:883: (1) ranges with no lease outside of node 3: []string{"24"}
Help

See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

Same failure on other branches

- #83372 roachtest: transfer-leases/signal failed [presumed same as #83261] [C-test-failure O-roachtest O-robot T-kv branch-master]

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-18097

aayushshah15 commented 2 years ago

This test has been flakey for the last 3 months, so this is not a new failure unique to 22.1.6. I've also been unable to reproduce this after ~25 runs~ 75 runs. So, I'm removing the release-blocker label from this while we investigate.

github-actions[bot] commented 1 year ago

We have marked this test failure issue as stale because it has been inactive for 1 month. If this failure is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 5 days to keep the test failure queue tidy.