cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260913: cli: TestConcurrentZip failed

Open
#175,608 2 comments 0 reactions 0 assignees View on GitHub
branch-basalt-26.3.2-rc-20260913 C-test-failure O-robot release-blocker T-observability
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

cli.TestConcurrentZip [failed](https://mesolite.cluster.engflow.com/invocations/default/aacf9200-9610-4f96-aeec-bfd38def6fda?testReportRun=1&testReportShard=5&testReportAttempt=1#targets-Ly9wa2cvY2xpOmNsaV90ZXN0) on basalt-26.3.2-rc-20260913 @ [c6a822fb5ec0b622c713fccacb82159d1b60bbcd](https://github.com/cockroachdb/cockroach/commits/c6a822fb5ec0b622c713fccacb82159d1b60bbcd):

```
=== RUN TestConcurrentZip
test_log_scope.go:172: test logs captured to: outputs.zip/logTestConcurrentZip823042293
test_log_scope.go:82: use -show-logs to present logs inline
test_log_scope.go:172: test logs captured to: outputs.zip/logTestConcurrentZip4035946192
[debug --host=127.0.0.1:36651 --insecure=true zip --timeout=30s --cpu-profile-duration=0s --validate-zip-file=false --cluster-name=TestCluster-oiBJLYVdZf /dev/null]
zip_test.go:472:
/mnt/engflow/worker/work/3/exec/bazel-out/k8-fastbuild/bin/pkg/cli/cli_test_/cli_test.runfiles/com_github_cockroachdb_cockroach/pkg/cli/testdata/zip/testzip_concurrent:1:
zip
output didn't match expected:
@@ -122,13 +122,13 @@
[node 1] writing ranges: writing JSON output: debug/nodes/1/ranges.json...
[node 2] node status...
[node 2] node status: done
[node 2] node status: writing JSON output: debug/nodes/2/status.json...
[node 2] requesting cpu profile list...
+[node 2] requesting cpu profile list: WARNING: 1 log entries in clitest.1c518c16-196e-4d4e-aa2b-4ffdc84f7b5b.roach.2026-09-18T07_49_04Z.000536.log mentioned sensitive cluster settings and were scrubbed client-side (0 were not redactable and were replaced entirely)
[node 2] requesting cpu profile list: creating error output: debug/nodes/2/cpuprof.err.txt...
[node 2] requesting cpu profile list: done
-[node 2] requesting cpu profile list: last request failed: rpc error: ...
[node 2] requesting cpu profile list: received response...
[node 2] requesting data for debug/nodes/2/details...
[node 2] requesting data for debug/nodes/2/details: done
[node 2] requesting data for debug/nodes/2/details: received response...
[node 2] requesting data for debug/nodes/2/details: writing JSON output: debug/nodes/2/details.json...
@@ -252,6 +252,7 @@
[node 3] writing ranges: writing JSON output: debug/nodes/3/ranges.json...
[node ?] ? log files found
[node ?] ? log files found
[node ?] ? log files found
debug zip --timeout=30s --cpu-profile-duration=0s --validate-zip-file=false --cluster-name= /dev/null
+last request failed: rpc error: ...

panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestConcurrentZip4035946192
panic.go:694: -- test log scope end --
--- FAIL: TestConcurrentZip (18.17s)
```

Parameters:
- attempt=1
- deadlock=true
- run=1
- shard=5
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

Same failure on other branches

- #175032 cli: TestConcurrentZip failed [C-test-failure O-robot T-observability branch-release-25.4.17-rc release-blocker]
- #174845 basalt-26.3: cli: TestConcurrentZip failed [C-test-failure O-robot T-observability branch-basalt-26.3 release-blocker]
- #174844 release-26.2: cli: TestConcurrentZip failed [C-test-failure O-robot T-observability branch-release-26.2]
- #174810 cli: TestConcurrentZip failed [C-test-failure O-robot T-observability branch-release-25.2.24-rc release-blocker]

/cc @cockroachlabs/obs-prs @cockroachlabs/server @cockroachlabs/obs-india-prs

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestConcurrentZip.*&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 with TestConcurrentZip in pkg/cli/zip_test.go around line 472 and compare its expected output in pkg/cli/testdata/zip/testzip_concurrent. Reproduce the failure using the linked test report and captured logs, then determine why concurrent runs produce differing warnings or request errors. Done means the test is stable and its expected output matches the intended CLI behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, testing-qa
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.