cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260908: sql/sqlstats/sslocal: TestNodeLocalInMemoryViewDoesNotReturnPersistedStats failed

Open
#175,657 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

branch-basalt-26.3.2-rc-20260908 C-test-failure O-robot release-blocker T-observability
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

sql/sqlstats/sslocal.TestNodeLocalInMemoryViewDoesNotReturnPersistedStats failed on basalt-26.3.2-rc-20260908 @ 807558e5e81666af257c811e925e4cae570abc28:

=== RUN   TestNodeLocalInMemoryViewDoesNotReturnPersistedStats
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestNodeLocalInMemoryViewDoesNotReturnPersistedStats3914923120
    test_log_scope.go:82: use -show-logs to present logs inline
    test_server_shim.go:168: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.

Parameters:

  • attempt=1
  • race=true
  • run=2
  • shard=1
Help

See also: How To Investigate a Go Test Failure (internal)

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

This test on roachdash | Improve this report!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with sql/sqlstats/sslocal.TestNodeLocalInMemoryViewDoesNotReturnPersistedStats and reproduce the race-enabled failure using the linked test report and captured logs. Trace the test setup and persisted-stats boundary; done means the test passes reliably on the reported release candidate and the regression is covered.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.