cockroachdb / cockroachdb/cockroach
sql/sqlstats/sslocal: TestNodeLocalInMemoryViewDoesNotReturnPersistedStats failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
sql/sqlstats/sslocal.TestNodeLocalInMemoryViewDoesNotReturnPersistedStats [failed](https://mesolite.cluster.engflow.com/invocations/default/5bfb4faf-02ac-4445-8fa2-1f163941e06f?testReportRun=2&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvc3FsL3NxbHN0YXRzL3NzbG9jYWw6c3Nsb2NhbF90ZXN0) on master @ [5318641d2b0ff04dbdaced9f83ecb0d692f697b6](https://github.com/cockroachdb/cockroach/commits/5318641d2b0ff04dbdaced9f83ecb0d692f697b6):
```
=== RUN TestNodeLocalInMemoryViewDoesNotReturnPersistedStats
test_log_scope.go:172: test logs captured to: outputs.zip/logTestNodeLocalInMemoryViewDoesNotReturnPersistedStats1220562002
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.
```
Parameters:
- attempt=1
- race=true
- run=2
- shard=3
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Same failure on other branches
- #174245 basalt-26.3: sql/sqlstats/sslocal: TestNodeLocalInMemoryViewDoesNotReturnPersistedStats failed [C-test-failure O-robot T-observability branch-basalt-26.3 release-blocker]
/cc @cockroachlabs/obs-prs
[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-68152
Contributor guide
Research direction
Start with sql/sqlstats/sslocal.TestNodeLocalInMemoryViewDoesNotReturnPersistedStats and reproduce it with the reported race=true, run=2, and shard=3 parameters. Inspect the captured outputs.zip logs and the linked test report to determine why the test fails; done means the test passes reliably on master and the underlying regression is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, observability, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100