cockroachdb / cockroachdb/cockroach

kv/kvserver/loqrecovery: TestRetrieveRangeStatus failed

Open
#175,648 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

branch-master C-test-failure O-robot release-blocker T-kv
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR metrics pending

Description

kv/kvserver/loqrecovery.TestRetrieveRangeStatus failed on master @ 61382aad0bf980a4a5547d80a5f1a9bd894678f9:

=== RUN   TestRetrieveRangeStatus
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestRetrieveRangeStatus2230058167
    test_log_scope.go:82: use -show-logs to present logs inline
    test_server_shim.go:146: using test tenant configuration from testserver factory defaults
    server_integration_test.go:591: failed to find scratch range in unavailable ranges
    panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestRetrieveRangeStatus2230058167
--- FAIL: TestRetrieveRangeStatus (103.05s)

Parameters:

  • attempt=1
  • deadlock=true
  • run=3
  • shard=1
Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachlabs/kv-triage

Improve this report!

Jira issue: CRDB-68548

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 kv/kvserver/loqrecovery.TestRetrieveRangeStatus and the linked test report, then inspect the failure at server_integration_test.go:591. Use the captured test logs in outputs.zip/logTestRetrieveRangeStatus2230058167 to determine why the scratch range is not found in unavailable ranges. Done means the test reliably passes without that failure.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.