cockroachdb / cockroachdb/cockroach
basalt-26.3.2-rc-20260908: crosscluster/logical/txnmode: TestTxnModePauseResume failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
crosscluster/logical/txnmode.TestTxnModePauseResume [failed](https://mesolite.cluster.engflow.com/invocations/default/5d15a619-5664-4606-90d0-90e2519cd159?testReportRun=1&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvY3Jvc3NjbHVzdGVyL2xvZ2ljYWwvdHhubW9kZTp0eG5tb2RlX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):
```
=== RUN TestTxnModePauseResume
test_log_scope.go:172: test logs captured to: outputs.zip/logTestTxnModePauseResume1608244860
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.
utils.go:54: waiting for logical replication job 1209876429588299777 to reach replicated time of 1789295392.476612216,0
utils.go:54: waiting for logical replication job 1209876429588299777 to reach replicated time of 1789295445.336004901,0
```
Parameters:
- attempt=1
- race=true
- run=1
- 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
- #174409 basalt-26.3: crosscluster/logical/txnmode: TestTxnModePauseResume failed [A-cdc C-test-failure O-robot T-cdc branch-basalt-26.3 release-blocker]
/cc @cockroachlabs/cdc
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestTxnModePauseResume.*&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 the linked test report and captured logs for crosscluster/logical/txnmode.TestTxnModePauseResume, then inspect test_log_scope.go, test_server_shim.go, and utils.go around the reported wait for the logical replication job. Reproduce the test with the shown commit and race parameters. Done means identifying and fixing the failure so the test passes reliably on the release branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100