cockroachdb / cockroachdb/cockroach
release-26.3: sql: TestContentionLoggingIntegration failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
sql.TestContentionLoggingIntegration [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/21521734?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/21521734?buildTab=artifacts#/) on release-26.3 @ [7fc12125563adc1e1e4455b002530f7a3f440dc2](https://github.com/cockroachdb/cockroach/commits/7fc12125563adc1e1e4455b002530f7a3f440dc2):
```
=== RUN TestContentionLoggingIntegration
test_log_scope.go:172: test logs captured to: /artifacts/tmp/_tmp/492cc08314ebb30515b6f60e383090f4/logTestContentionLoggingIntegration1475963472
test_log_scope.go:82: use -show-logs to present logs inline
crdb_internal_test.go:880: condition failed to evaluate within 45s: from crdb_internal_test.go:886: no contention log events captured yet
goroutine dump: /artifacts/tmp/_tmp/492cc08314ebb30515b6f60e383090f4/goroutine_dump_2625635964.txt
panic.go:694: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/492cc08314ebb30515b6f60e383090f4/logTestContentionLoggingIntegration1475963472
--- FAIL: TestContentionLoggingIntegration (47.14s)
```
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Same failure on other branches
- #170308 sql: TestContentionLoggingIntegration failed [C-test-failure O-robot T-sql-queries branch-master]
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestContentionLoggingIntegration.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-68489
Contributor guide
Research direction
Start with TestContentionLoggingIntegration in crdb_internal_test.go and reproduce the failure on release-26.3. Inspect the linked TeamCity logs, artifacts, and goroutine dump to determine why no contention log events are captured; done means the test reliably captures the expected events without timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100