cockroachdb / cockroachdb/cockroach

multitenant/tenantcostclient: TestRUSettingsChanged failed

Closed
#175,006 2 comments 0 reactions 0 assignees View on GitHub
branch-master C-test-failure O-robot T-db-server
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

multitenant/tenantcostclient.TestRUSettingsChanged [failed](https://mesolite.cluster.engflow.com/invocations/default/5bfb4faf-02ac-4445-8fa2-1f163941e06f?testReportRun=3&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvbXVsdGl0ZW5hbnQvdGVuYW50Y29zdGNsaWVudDp0ZW5hbnRjb3N0Y2xpZW50X3Rlc3Q=) on master @ [5318641d2b0ff04dbdaced9f83ecb0d692f697b6](https://github.com/cockroachdb/cockroach/commits/5318641d2b0ff04dbdaced9f83ecb0d692f697b6):

```
=== RUN TestRUSettingsChanged
test_log_scope.go:172: test logs captured to: outputs.zip/logTestRUSettingsChanged2346241425
test_log_scope.go:82: use -show-logs to present logs inline
```

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/server

[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-68158

Contributor guide

Open the contributing guide

Research direction

Run multitenant/tenantcostclient.TestRUSettingsChanged with the reported race=true, run=3, and shard=1 settings, then inspect the linked test report and captured logs. Done means identifying the failure cause and making the test pass reliably on master; the issue does not name a source file or expected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.