cockroachdb / cockroachdb/cockroach

backup: TestRestoreEntryCover9 failed

Open
#175,577 1 comment 0 reactions 0 assignees View on GitHub
A-disaster-recovery branch-release-25.4.17-rc C-test-failure O-robot release-blocker T-disaster-recovery
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

backup.TestRestoreEntryCover9 [failed](https://mesolite.cluster.engflow.com/invocations/default/37ef2b48-3634-4013-aaa2-520e5a9ed408?testReportRun=3&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvYmFja3VwOmJhY2t1cF90ZXN0) on release-25.4.17-rc @ [3981ecae25dbf445f122d375bf813b8859158a14](https://github.com/cockroachdb/cockroach/commits/3981ecae25dbf445f122d375bf813b8859158a14):

```
=== RUN TestRestoreEntryCover9
test_log_scope.go:171: test logs captured to: outputs.zip/logTestRestoreEntryCover9400285324
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:154: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
testutils.go:307: no Invalid Descriptors
```

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/disaster-recovery

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestRestoreEntryCover9.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Contributor guide

Open the contributing guide

Research direction

Start by rerunning backup.TestRestoreEntryCover9 with the reported race=true, run=3, and shard=1 parameters, then inspect the captured logs at outputs.zip/logTestRestoreEntryCover9400285324. Read test_log_scope.go and test_server_shim.go for the test harness context; done means identifying and fixing the failure so the test passes reliably under the reported configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.