cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260908: sql/stats: TestCacheAutoRefresh failed

Open
#174,912 2 comments 0 reactions 0 assignees View on GitHub
branch-basalt-26.3.2-rc-20260908 C-test-failure O-robot T-sql-queries
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

sql/stats.TestCacheAutoRefresh [failed](https://mesolite.cluster.engflow.com/invocations/default/8e093717-3329-4dab-8a28-3ae7ce8b0293?testReportRun=3&testReportShard=7&testReportAttempt=1#targets-Ly9wa2cvc3FsL3N0YXRzOnN0YXRzX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):

```
=== RUN TestCacheAutoRefresh
test_log_scope.go:172: test logs captured to: outputs.zip/logTestCacheAutoRefresh3323407664
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=3
- shard=7
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestCacheAutoRefresh.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Contributor guide

Open the contributing guide

Research direction

Start with the linked test report for sql/stats.TestCacheAutoRefresh and inspect the captured logs from the failing race-enabled run. Reproduce the failure with the recorded commit and parameters, then trace the cause in the SQL statistics cache-refresh code. Done means the underlying failure is fixed and the test passes reliably under race detection.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
databases, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.