cockroachdb / cockroachdb/cockroach
basalt-26.3: 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/68c27e32-985d-4b3d-b498-ca4f62daf522?testReportRun=1&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvY3Jvc3NjbHVzdGVyL2xvZ2ljYWwvdHhubW9kZTp0eG5tb2RlX3Rlc3Q=) on basalt-26.3 @ [ac8dd0a5e6674df51e4d0f0f292029b14dbc084c](https://github.com/cockroachdb/cockroach/commits/ac8dd0a5e6674df51e4d0f0f292029b14dbc084c):
```
=== RUN TestTxnModePauseResume
test_log_scope.go:172: test logs captured to: outputs.zip/logTestTxnModePauseResume2097593509
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 1206191730928648193 to reach replicated time of 1788170912.330480049,0
utils.go:54: waiting for logical replication job 1206191730928648193 to reach replicated time of 1788170966.037258082,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)
/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)
Jira issue: CRDB-67684
Contributor guide
Research direction
Start with crosscluster/logical/txnmode.TestTxnModePauseResume and reproduce the failure using the reported race=true parameters. Inspect the captured outputs.zip logs and the waiting messages from utils.go, with test_log_scope.go and test_server_shim.go providing the test-harness context. Done means identifying the failure cause and making the test pass reliably.
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
- 38/100