cockroachdb / cockroachdb/cockroach
acceptance: TestDockerCLI_test_exec_log failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
acceptance.TestDockerCLI_test_exec_log [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_Acceptance/21508158?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_Acceptance/21508158?buildTab=artifacts#/) on master @ [6e5cd3732047fcc0aec0fa37005cf1aebd0ff3e8](https://github.com/cockroachdb/cockroach/commits/6e5cd3732047fcc0aec0fa37005cf1aebd0ff3e8):
```
=== RUN TestDockerCLI_test_exec_log
test_log_scope.go:172: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/_tmp/10ec824bdba8835cc2b262dc9f0dd439/logTestDockerCLI_test_exec_log561225217
test_log_scope.go:82: use -show-logs to present logs inline
generated_cli_test.go:217: -- test log scope end --
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/_tmp/10ec824bdba8835cc2b262dc9f0dd439/logTestDockerCLI_test_exec_log561225217
--- FAIL: TestDockerCLI_test_exec_log (7.81s)
=== RUN TestDockerCLI_test_exec_log/test_exec_log.tcl
util_docker.go:256: non-zero exit code: 1
--- FAIL: TestDockerCLI_test_exec_log/test_exec_log.tcl (5.34s)
```
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
/cc @cockroachlabs/sql-foundations
[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-68114
Contributor guide
Research direction
Start with the TeamCity build log and artifacts for TestDockerCLI_test_exec_log, then inspect the failure path through generated_cli_test.go, util_docker.go, and test_log_scope.go. Reproduce the test on the referenced commit and identify why test_exec_log.tcl exits with code 1; done means the acceptance test passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100