cockroachdb / cockroachdb/cockroach
pkg/server/storage_api/storage_api_test: TestLivenessAPI failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
pkg/server/storage_api/storage_api_test.TestLivenessAPI [failed](https://mesolite.cluster.engflow.com/invocations/default/d57b21c3-5ccf-4825-976c-36ae3bc31258?testReportRun=3&testReportShard=4&testReportAttempt=1#targets-Ly9wa2cvc2VydmVyL3N0b3JhZ2VfYXBpOnN0b3JhZ2VfYXBpX3Rlc3Q=) on master @ [8f2e289027997fe6fb7582a49f5233fedcf8b373](https://github.com/cockroachdb/cockroach/commits/8f2e289027997fe6fb7582a49f5233fedcf8b373):
```
=== RUN TestLivenessAPI
test_log_scope.go:172: test logs captured to: outputs.zip/logTestLivenessAPI309108412
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:168: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
health_test.go:140: condition failed to evaluate within 3m45s: from slinstance.go:381: grant-admin: session record deleted
goroutine dump: /mnt/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/testlogs/pkg/server/storage_api/storage_api_test/shard_4_of_8_run_3_of_3/test.outputs/goroutine_dump_2156172949.txt
panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestLivenessAPI309108412
--- FAIL: TestLivenessAPI (1347.60s)
```
Parameters:
- attempt=1
- race=true
- run=3
- shard=4
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Same failure on other branches
- #175298 basalt-26.3.2-rc-20260908: pkg/server/storage_api/storage_api_test: TestLivenessAPI failed [C-test-failure O-robot T-observability branch-basalt-26.3.2-rc-20260908 release-blocker]
/cc @cockroachlabs/obs-prs
[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-68504
Contributor guide
Research direction
Start with pkg/server/storage_api/storage_api_test.TestLivenessAPI and inspect the captured logs from the linked test report. Read health_test.go around line 140, slinstance.go around line 381, and the test_server_shim.go comments to understand the session-record deletion. Done means the liveness test passes reliably under the reported race, shard, and run conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100