cockroachdb / cockroachdb/cockroach
basalt-26.3.2-rc-20260908: crosscluster/logical/txnmode: TestTxnModeSmoketest failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
crosscluster/logical/txnmode.TestTxnModeSmoketest [failed](https://mesolite.cluster.engflow.com/invocations/default/f0916551-4348-4015-a964-7d1ed87aeec5?testReportRun=2&testReportShard=2&testReportAttempt=1#targets-Ly9wa2cvY3Jvc3NjbHVzdGVyL2xvZ2ljYWwvdHhubW9kZTp0eG5tb2RlX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):
```
=== RUN TestTxnModeSmoketest
test_log_scope.go:172: test logs captured to: outputs.zip/logTestTxnModeSmoketest2868371376
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 1209303912567341057 to reach replicated time of 1789120671.356014815,0
utils.go:54: waiting for logical replication job 1209303912567341057 to reach replicated time of 1789120701.217810871,0
```
Parameters:
- attempt=1
- race=true
- run=2
- shard=2
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
/cc @cockroachlabs/cdc
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestTxnModeSmoketest.*&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 crosscluster/logical/txnmode.TestTxnModeSmoketest and open the linked invocation, including the captured outputs.zip logs. Read test_server_shim.go and utils.go around the shared virtual cluster and logical replication wait messages. Done means identifying the cause of the stalled replication wait and getting the test to complete successfully.
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
- 42/100