cockroachdb / cockroachdb/cockroach
basalt-26.3.2-rc-20260914: sql/sqlstats/sslocal: TestTransactionLatencies failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
sql/sqlstats/sslocal.TestTransactionLatencies [failed](https://mesolite.cluster.engflow.com/invocations/default/e97a94d3-9833-4a85-9ee3-760c3aa12029?testReportRun=3&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvc3FsL3NxbHN0YXRzL3NzbG9jYWw6c3Nsb2NhbF90ZXN0) on basalt-26.3.2-rc-20260914 @ [d3eb08ebdd1dacc8d3dac0b107a7db5929e09969](https://github.com/cockroachdb/cockroach/commits/d3eb08ebdd1dacc8d3dac0b107a7db5929e09969):
```
=== RUN TestTransactionLatencies
test_log_scope.go:172: test logs captured to: outputs.zip/logTestTransactionLatencies1674460707
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.
sql_stats_test.go:1923: -- test log scope end --
test logs left over in: outputs.zip/logTestTransactionLatencies1674460707
--- FAIL: TestTransactionLatencies (18.17s)
=== RUN TestTransactionLatencies/with_intermediate_observer_statements
sql_stats_test.go:1900: error executing query="COMMIT" args=[]: pq: restart transaction: TransactionRetryWithProtoRefreshError: TransactionRetryError: retry txn (RETRY_ASYNC_WRITE_FAILURE - missing intent on: /Tenant/10/Table/104/1/1211004206580400129/0): "sql txn" meta={id=377d0238 key=/Tenant/10/Table/104/1/1211004195807920129/0 iso=Serializable pri=0.01776847 epo=0 ts=1789639552.397841904,2 min=1789639551.550593526,0 seq=11} lock=true stat=PENDING rts=1789639552.397841904,2 gul=1789639552.050593526,0 obs={n1@1789639551.550593526,0}
HINT: See: https://www.cockroachlabs.com/docs/v26.3/transaction-retry-error-reference.html#retry_async_write_failure
--- FAIL: TestTransactionLatencies/with_intermediate_observer_statements (4.16s)
```
Parameters:
- attempt=1
- race=true
- run=3
- shard=1
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Same failure on other branches
- #175299 basalt-26.3.2-rc-20260908: sql/sqlstats/sslocal: TestTransactionLatencies failed [C-test-failure O-robot T-observability branch-basalt-26.3.2-rc-20260908 release-blocker]
- #173941 basalt-26.3: sql/sqlstats/sslocal: TestTransactionLatencies failed [C-test-failure O-robot T-observability branch-basalt-26.3 release-blocker]
/cc @cockroachlabs/obs-prs
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestTransactionLatencies.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Contributor guide
Research direction
Start with sql/sqlstats/sslocal.TestTransactionLatencies in sql_stats_test.go, especially the failure at lines 1900 and 1923, and inspect the captured test logs referenced in the report. Compare the repeated failures in issues #175299 and #173941 to identify the cause of the transaction retry; done means the test passes reliably on the affected basalt branches.
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