-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cli: TestUnavailableZip failed #116228
Labels
A-observability-inf
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
P-1
Issues/test failures with a fix SLA of 1 month
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
Milestone
Comments
cli.TestUnavailableZip failed with artifacts on master @ 52329bc384068b9ea3e0c0e1100397f537dd2b89:
|
cli.TestUnavailableZip failed with artifacts on master @ 512fc0e95bbd6690740c6e77b4efce6a4edd58b2:
|
cli.TestUnavailableZip failed with artifacts on master @ 6556ee673bfc8938511981ea7892d00d75448cfa:
|
cli.TestUnavailableZip failed on master @ d2d974202781321ddb4fb1115c68fe7566ab9d06:
Parameters:
|
dhartunian
added a commit
to dhartunian/cockroach
that referenced
this issue
Dec 28, 2023
Currently, these tests fail in CI with a nil pointer at runtime when we call `c.t.Fail` when an error is produced. This change removes the sharing of the `t` variable with `TestCLI` since it seems to result in a conflict between the outer test code and what runs inside `RunWithCapture`. I was unable to reproduce the error locally and do not have further clues. My hope is that, the simplified error handling will surface the actual error in CI instead of the continued nil pointer exception. Resolves: cockroachdb#116228 Epic: None Release note: None
craig bot
pushed a commit
that referenced
this issue
Dec 28, 2023
117137: cli: remove `t` field from `TestCLI` usage r=abarganier a=dhartunian Currently, these tests fail in CI with a nil pointer at runtime when we call `c.t.Fail` when an error is produced. This change removes the sharing of the `t` variable with `TestCLI` since it seems to result in a conflict between the outer test code and what runs inside `RunWithCapture`. I was unable to reproduce the error locally and do not have further clues. My hope is that, the simplified error handling will surface the actual error in CI instead of the continued nil pointer exception. Resolves: #116228 Epic: None Release note: None Co-authored-by: David Hartunian <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-observability-inf
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
P-1
Issues/test failures with a fix SLA of 1 month
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
cli.TestUnavailableZip failed with artifacts on master @ 96374f0c0c4758c93403631ce49c1c7bc93ef42e:
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-34527
The text was updated successfully, but these errors were encountered: