oxidecomputer / oxidecomputer/cockroach

test flake in pkg/kv/kvserver: `TestConsistencyQueueRecomputeStats`

Open
#72 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

flake
Dominant language
Go
Stars
34
Forks
8
PR merge metrics
No merged PRs in 30d

Description

https://github.com/oxidecomputer/cockroach/pull/71/checks?check_run_id=83094338730

https://buildomat.eng.oxide.computer/wg/0/details/01KVVHJPQXVET94W0VYMV62WMJ/7hy7LsagYaAEQfCAnD3rnffUMvQhscCfJjTkuwqnB733LNlv/01KVVHK33CFVTYAXBXZMX81PSS#S2687

--- FAIL: TestConsistencyQueueRecomputeStats (5.01s)
    test_log_scope.go:79: test logs captured to: /tmp/logTestConsistencyQueueRecomputeStats1493483488
    test_log_scope.go:80: use -show-logs to present logs inline
    --- FAIL: TestConsistencyQueueRecomputeStats/hadEstimates=false (2.94s)
        consistency_queue_test.go:683: still have a SysCount of 123009
    consistency_queue_test.go:492: -- test log scope end --

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with pkg/kv/kvserver/consistency_queue_test.go, especially TestConsistencyQueueRecomputeStats and its hadEstimates=false subtest. Reproduce the failure with the targeted Go test and use -show-logs or the linked build logs to inspect the reported SysCount. Done means the test passes reliably without the flake.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.