cockroachdb / cockroachdb/cockroach
roachtest: monitor_failure failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.monitor_failure [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAwsBazel/17918665?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAwsBazel/17918665?buildTab=artifacts#/kv0/enc=false/nodes=1/cpu=32) on release-24.3.1-rc @ [f5d0998f1abcaa20acc142485788aa4fe08a0ee3](https://github.com/cockroachdb/cockroach/commits/f5d0998f1abcaa20acc142485788aa4fe08a0ee3):
```
test kv0/enc=false/nodes=1/cpu=32 failed: (cluster.go:2455).Run: context canceled
(monitor.go:149).Wait: monitor failure: monitor user task failed: t.Fatal() was called
EOF [owner=test-eng]
test artifacts and logs in: /artifacts/kv0/enc=false/nodes=1/cpu=32/cpu_arch=arm64/run_1
```
Parameters:
- arch=arm64
- cloud=aws
- coverageBuild=false
- cpu=32
- encrypted=false
- fs=ext4
- localSSD=true
- 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_
Same failure on other branches
- #134929 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.3.0-rc]
- #132978 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.3]
- #132025 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.2]
- #131734 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.2.4-rc]
- #130292 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.1]
- #126792 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-master]
/cc @cockroachdb/test-eng
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*monitor_failure.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-45035
Contributor guide
Research direction
Start with the linked TeamCity logs and artifacts for kv0/enc=false/nodes=1/cpu=32, then read the failure locations cited in cluster.go:2455 and monitor.go:149 and the roachtest README. Compare this failure with the related issues and roachdash results; done means identifying the recurring monitor_failure cause and documenting or validating a fix across the affected branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100