-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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's java tests sometimes fail with all test cases passed but TEST_PREMATURE_EXIT_FILE exists #24655
Labels
P1
I'll work on this now. (Assignee required)
team-Rules-Java
Issues for Java rules
type: bug
untriaged
Comments
meteorcloudy
assigned sgowroji, iancha1992, satyanandak and meteorcloudy and unassigned sgowroji, iancha1992 and satyanandak
Dec 12, 2024
meteorcloudy
added
team-Rules-Java
Issues for Java rules
P1
I'll work on this now. (Assignee required)
labels
Dec 12, 2024
@bazel-io fork 8.0.1 |
Found a way to reproduce locally:
If step 2 fails, then step 3 should be able to reproduce the failure with a given chance. And once it's reproduced and cached, rerunning will show the same error again. |
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this issue
Dec 12, 2024
`TEST_PREMATURE_EXIT_FILE` was not cleaned up between test attempts (--flaky_test_attempts). Fixes bazelbuild#24655 Closes bazelbuild#24657. PiperOrigin-RevId: 705495967 Change-Id: Ic4d4be1e72230c3a6bc45c9f372d1188fefad201
github-merge-queue bot
pushed a commit
that referenced
this issue
Dec 12, 2024
`TEST_PREMATURE_EXIT_FILE` was not cleaned up between test attempts (--flaky_test_attempts). Fixes #24655 Closes #24657. PiperOrigin-RevId: 705495967 Change-Id: Ic4d4be1e72230c3a6bc45c9f372d1188fefad201 Commit b33d51f Co-authored-by: Yun Peng <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P1
I'll work on this now. (Assignee required)
team-Rules-Java
Issues for Java rules
type: bug
untriaged
Description of the bug:
Example: https://buildkite.com/bazel/bazel-bazel/builds/30505#0193b7e6-4a47-41a7-b5f8-cf4ffa391104
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
So far only seen on CI, not reproducible locally
Which operating system are you running Bazel on?
Linux
What is the output of
bazel info release
?8.0.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
Yes, only appeared with Bazel 8.0.0, probably triggered by #23284, but it may not be the root cause.
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: