cockroachdb / cockroachdb/cockroach

release-26.2: cli: TestConcurrentZip failed

Open
#174,844 2 comments 0 reactions 0 assignees View on GitHub
branch-release-26.2 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/f8dbed09-386a-4b73-b976-7a3566d165c8?testReportRun=3&testReportShard=8&testReportAttempt=1#targets-Ly9wa2cvY2xpOmNsaV90ZXN0) on release-26.2 @ [af7b3170ea0bf609c97954e8db045e95ee3c430b](https://github.com/cockroachdb/cockroach/commits/af7b3170ea0bf609c97954e8db045e95ee3c430b):

```
=== RUN TestConcurrentZip
test_log_scope.go:172: test logs captured to: outputs.zip/logTestConcurrentZip751787196
test_log_scope.go:82: use -show-logs to present logs inline
test_log_scope.go:172: test logs captured to: outputs.zip/logTestConcurrentZip3153847978
[debug --host=127.0.0.1:45395 --insecure=true zip --timeout=30s --cpu-profile-duration=0s --validate-zip-file=false --cluster-name=TestCluster-5FRmV3RuBZ /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:
@@ -204,13 +204,13 @@
[node 3] requesting data for debug/nodes/3/mma_state...
[node 3] requesting data for debug/nodes/3/mma_state: done
[node 3] requesting data for debug/nodes/3/mma_state: received response...
[node 3] requesting data for debug/nodes/3/mma_state: writing JSON output: debug/nodes/3/mma_state.json...
[node 3] requesting engine stats...
+[node 3] requesting engine stats: WARNING: 1 log entries in clitest.01dc8241-6d50-430d-a76b-d9a6d02372d9.roach.2026-09-08T07_48_18Z.000301.log mentioned sensitive cluster settings and were scrubbed client-side (0 were not redactable and were replaced entirely)
[node 3] requesting engine stats: done
[node 3] requesting engine stats: received response...
-[node 3] requesting engine stats: writing binary output: debug/nodes/3/lsm.txt...
[node 3] requesting execution trace list...
[node 3] requesting execution trace list: creating error output: debug/nodes/3/executiontraces.err.txt...
[node 3] requesting execution trace list: done
[node 3] requesting execution trace list: last request failed: rpc error: ...
[node 3] requesting execution trace list: received response...
@@ -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
+writing binary output: debug/nodes/3/lsm.txt...

panic.go:615: -- test log scope end --
panic.go:615: -- test log scope end --
test logs left over in: outputs.zip/logTestConcurrentZip3153847978
--- FAIL: TestConcurrentZip (17.75s)
```

Parameters:
- attempt=1
- deadlock=true
- run=3
- shard=8
Help

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

Same failure on other branches

- #174810 cli: TestConcurrentZip failed [C-test-failure O-robot T-db-server 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)

Jira issue: CRDB-68034

Contributor guide

Open the contributing guide

Research direction

Start with pkg/cli/zip_test.go at TestConcurrentZip and the testdata/zip/testzip_concurrent fixture. Reproduce the release-26.2 failure using the reported test target and inspect the captured logs and output diff. Done means the concurrent zip test passes with stable expected output.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.