New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ccl/multitenantccl/tenantcostclient: TestScheduledJobsConsumption failed #122336
Comments
cc @cockroachdb/disaster-recovery |
ccl/multitenantccl/tenantcostclient.TestScheduledJobsConsumption failed on release-24.1 @ 273a97e181d634e5d5d51ac7d3e05f3f4f31887a:
Parameters:
Same failure on other branches
|
Flake around expected number read batches during server startup. This doesn't need to block the release. |
ccl/multitenantccl/tenantcostclient.TestScheduledJobsConsumption failed on release-24.1 @ 88c9d88cb0093d35f2d630137fd178518aa48569:
Parameters:
Same failure on other branches
|
Did you determine that with a bisect? It looks like the test disables auto-stats collection:
Does |
No, I didn't do a bisect, but I'm fairly confident that #121861 is what triggered these flakes (the test starting flaking on all branches after the backport but not on master where we have an additional commit). Yes, we do call Not sure whether we just want to skip this test in some configs. I wonder whether we should introduce a testing knob that disables "initial table collection" in |
ccl/multitenantccl/tenantcostclient.TestScheduledJobsConsumption failed on release-24.1 @ 3f3127b8b592b9c63df76e47cb9f0a3b47357f62:
Parameters:
Same failure on other branches
|
cc @cockroachdb/disaster-recovery |
ccl/multitenantccl/tenantcostclient.TestScheduledJobsConsumption failed on release-24.1 @ 6e3e9e6012dc04dabc64333a87e77a80d9f9d46b:
Parameters:
attempt=1
race=true
run=1
shard=1
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-37810
The text was updated successfully, but these errors were encountered: