-
Notifications
You must be signed in to change notification settings - Fork 4k
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
bazel shell test succeeds even when one test case reported failed #12376
Labels
category: misc > testing
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Comments
meteorcloudy
added
type: bug
P1
I'll work on this now. (Assignee required)
category: misc > testing
labels
Oct 28, 2020
Just to add one more detail, the fail call can be replaced with |
Maybe caused by #12377 |
After removing
the test failed as expected... 😂 |
I only traced down to |
meteorcloudy
added
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
P2
We'll consider working on this in future. (Assignee optional)
and removed
P1
I'll work on this now. (Assignee required)
labels
Dec 4, 2020
meteorcloudy
added a commit
to meteorcloudy/bazel
that referenced
this issue
Dec 4, 2020
The stop_worker function in remote_utils.sh was broken with an unbounded variable error. This error somehow shadowed the return code of the test cases on macOS. Fixes bazelbuild#12377 Fixes bazelbuild#12376
meteorcloudy
added a commit
to meteorcloudy/bazel
that referenced
this issue
Dec 4, 2020
The stop_worker function in remote_utils.sh was broken with an unbounded variable error. This error somehow shadowed the return code of the test cases on macOS. Fixes bazelbuild#12377 Fixes bazelbuild#12376
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
category: misc > testing
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Description of the problem:
Bazel reports a shell test as passed when it actually fails.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
macOS
What's the output of
bazel info release
?3.7.0
The text was updated successfully, but these errors were encountered: