cockroachdb / cockroachdb/cockroach

basalt-26.3: sql/stmtdiagnostics: TestTxnRegistry_CancelRequest_MultiNode failed

Open
#174,820 2 comments 0 reactions 0 assignees View on GitHub
branch-basalt-26.3 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/stmtdiagnostics.TestTxnRegistry_CancelRequest_MultiNode [failed](https://mesolite.cluster.engflow.com/invocations/default/4d392fbc-9a9a-45a4-b5da-c259a95be606?testReportRun=3&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvc3FsL3N0bXRkaWFnbm9zdGljczpzdG10ZGlhZ25vc3RpY3NfdGVzdA==) on basalt-26.3 @ [30531f831e37dfb219a9b7d87cef860a3b64c094](https://github.com/cockroachdb/cockroach/commits/30531f831e37dfb219a9b7d87cef860a3b64c094):

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

- #173407 sql/stmtdiagnostics: TestTxnRegistry_CancelRequest_MultiNode failed [C-test-failure O-robot T-sql-queries branch-master]

[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)

Jira issue: CRDB-68014

Contributor guide

Open the contributing guide

Research direction

Start with sql/stmtdiagnostics.TestTxnRegistry_CancelRequest_MultiNode and inspect the linked test report and captured logs at outputs.zip/logTestTxnRegistry_CancelRequest_MultiNode3253541940. Read the comment at the top of test_server_shim.go to understand the injected virtual cluster, then compare the failure with prior issue #173407. Done means identifying and fixing the failure so the race-enabled multi-node test passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, distributed-systems, testing
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.