cockroachdb / cockroachdb/cockroach
multitenant/tenantcostclient: TestSQLLivenessExemption failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
multitenant/tenantcostclient.TestSQLLivenessExemption [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/21479324?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/21479324?buildTab=artifacts#/) on master @ [8972b883e97024e01ddf35c84e8744489f3c20b1](https://github.com/cockroachdb/cockroach/commits/8972b883e97024e01ddf35c84e8744489f3c20b1):
```
=== RUN TestSQLLivenessExemption
test_log_scope.go:172: test logs captured to: /artifacts/tmp/_tmp/66d4673abd02bb1635f55c7614269931/logTestSQLLivenessExemption3302796104
test_log_scope.go:82: use -show-logs to present logs inline
```
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
/cc @cockroachlabs/server
[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-67086
Contributor guide
Research direction
Start with the linked TeamCity log and artifacts for multitenant/tenantcostclient.TestSQLLivenessExemption, then run that test locally to reproduce the failure. Done means identifying the cause, making the test pass reliably, and confirming the result with the relevant test run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100