cockroachdb / cockroachdb/cockroach
basalt-26.3.2-rc-20260908: crosscluster/logical/txnmode: TestLDRReplicationLagPersistence failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
crosscluster/logical/txnmode.TestLDRReplicationLagPersistence [failed](https://mesolite.cluster.engflow.com/invocations/default/bb2803f0-20da-4132-9bf9-2818a577ee69?testReportRun=2&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvY3Jvc3NjbHVzdGVyL2xvZ2ljYWwvdHhubW9kZTp0eG5tb2RlX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):
```
=== RUN TestLDRReplicationLagPersistence
test_log_scope.go:172: test logs captured to: outputs.zip/logTestLDRReplicationLagPersistence3342893410
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 1210457042803982337 to reach replicated time of 1789472583.210633423,0
utils.go:54: waiting for logical replication job 1210457187370205185 to reach replicated time of 1789472621.450443656,0
```
Parameters:
- attempt=1
- race=true
- run=2
- shard=3
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:.*TestLDRReplicationLagPersistence.*&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.TestLDRReplicationLagPersistence and rerun it with the linked invocation and captured logs. Read the referenced test_log_scope.go, utils.go, and test_server_shim.go, then determine why the logical replication jobs do not reach the reported replicated times. Done means the test passes on the affected revision.
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
- 45/100