cockroachdb / cockroachdb/cockroach
roachtest: cdc/tpcc-1000/sink=kafka failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.cdc/tpcc-1000/sink=kafka [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAwsBazel/21476894?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAwsBazel/21476894?buildTab=artifacts#/cdc/tpcc-1000/sink=kafka) on release-25.4 @ [ad24655158d84347352f678499e7b2a3604385b6](https://github.com/cockroachdb/cockroach/commits/ad24655158d84347352f678499e7b2a3604385b6):
```
(test_runner.go:1493).runTest: test timed out (3h0m0s)
test artifacts and logs in: /artifacts/cdc/tpcc-1000/sink=kafka/cpu_arch=arm64/run_1
```
Parameters:
- arch=arm64
- cloud=aws
- coverageBuild=false
- cpu=16
- encrypted=false
- fs=ext4
- localSSD=true
- metamorphicLeases=default
- runtimeAssertionsBuild=false
- ssd=0
Help
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
_Grafana is not yet available for aws clusters_
/cc @cockroachlabs/cdc
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*cdc/tpcc-1000/sink=kafka.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-66998
Contributor guide
Research direction
Start with the TeamCity log and artifacts for roachtest cdc/tpcc-1000/sink=kafka on arm64, then read pkg/cmd/roachtest/README.md and the linked investigation guide. Determine why the test exceeded the three-hour timeout and document or implement a verified resolution, with the roachtest completing successfully afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kafka
- Domain
- databases, distributed-systems, stream-processing, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100