cockroachdb / cockroachdb/cockroach
crosscluster/producer: TestCompleteStreamReplication failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
crosscluster/producer.TestCompleteStreamReplication [failed](https://mesolite.cluster.engflow.com/invocations/default/d1b724db-dda0-45d8-9eba-e070f3c6b027?testReportRun=3&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvY3Jvc3NjbHVzdGVyL3Byb2R1Y2VyOnByb2R1Y2VyX3Rlc3Q=) on master @ [3ad8bd365c74c60df49d73491cc02463f3895038](https://github.com/cockroachdb/cockroach/commits/3ad8bd365c74c60df49d73491cc02463f3895038):
```
=== RUN TestCompleteStreamReplication
test_log_scope.go:172: test logs captured to: outputs.zip/logTestCompleteStreamReplication2700026139
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:639: DRPC is enabled (via testserver factory defaults)
```
Parameters:
- attempt=1
- race=true
- run=3
- shard=1
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
/cc @cockroachlabs/disaster-recovery
[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-66734
Contributor guide
Research direction
Start with the crosscluster/producer.TestCompleteStreamReplication test and inspect the captured logs at outputs.zip/logTestCompleteStreamReplication2700026139, using -show-logs if needed. Read the linked internal Go test failure investigation guide and determine the cause of the failure; done means the test passes reliably on master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100