basalt-26.3.2-rc-20260908: sql/stmtdiagnostics: TestTxnRegistry_CancelRequest_MultiNode failed

sql/stmtdiagnostics.TestTxnRegistry_CancelRequest_MultiNode [failed](https://mesolite.cluster.engflow.com/invocations/default/84483de1-b344-4bb7-a487-42863798b484?testReportRun=1&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvc3FsL3N0bXRkaWFnbm9zdGljczpzdG10ZGlhZ25vc3RpY3NfdGVzdA==) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):

```
=== RUN TestTxnRegistry_CancelRequest_MultiNode
test_log_scope.go:172: test logs captured to: outputs.zip/logTestTxnRegistry_CancelRequest_MultiNode503470632
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=1
- shard=3
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:.*TestTxnRegistry_CancelRequest_MultiNode.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Start with sql/stmtdiagnostics.TestTxnRegistry_CancelRequest_MultiNode and inspect the captured outputs.zip/logTestTxnRegistry_CancelRequest_MultiNode503470632 from the linked test report. Review test_server_shim.go and the internal test-failure investigation guide, then rerun the test with race=true to determine what reproduces. Done means identifying and addressing the cause of the multi-node test failure.

Written by the indexing model from the issue text.