//src/test/java/com/google/devtools/build/lib/platform:SystemMemoryPressureEventTest started failing pre- and post-submit #17410
Labels
macos-infra-update
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
coeuvre
pushed a commit
to coeuvre/bazel
that referenced
this issue
Feb 6, 2023
…ates. Related to bazelbuild#17410 and bazelbuild#17411. PiperOrigin-RevId: 506903607 Change-Id: Ic88de4caea5c14336774e53a9063a6beb260d515
coeuvre
pushed a commit
to coeuvre/bazel
that referenced
this issue
Feb 6, 2023
…ates. Related to bazelbuild#17410 and bazelbuild#17411. PiperOrigin-RevId: 506903607 Change-Id: Ic88de4caea5c14336774e53a9063a6beb260d515
ShreeM01
pushed a commit
that referenced
this issue
Feb 6, 2023
* Bazel CI: Disable tests that are failing due to infra upgrades. This change should unblock both pre- and post-submit. Related to #16526, #17407, #17408 and #17409. PiperOrigin-RevId: 506882975 Change-Id: If704c398546265eb22d58906eb28363b30ac00a2 * Bazel CI: Disable more tests that are likely failing due to infra updates. Related to #17410 and #17411. PiperOrigin-RevId: 506903607 Change-Id: Ic88de4caea5c14336774e53a9063a6beb260d515 * Disable python_version_test --------- Co-authored-by: Googler <[email protected]>
sgowroji
added
the
team-OSS
meteorcloudy
added
P2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug:
On Intel Macs:
https://storage.googleapis.com/bazel-untrusted-buildkite-artifacts/018616c9-35e4-4faa-bba2-a48690131cbd/src/test/java/com/google/devtools/build/lib/platform/SystemMemoryPressureEventTest/test_attempts/attempt_1.log from https://buildkite.com/bazel/bazel-bazel/builds/22029#018615ef-f8c8-4403-becd-de5678d18b43
Also failing in the presubmit: https://buildkite.com/bazel/google-bazel-presubmit/builds/63133#01861789-3330-4511-bb43-08a2ed784ae1
Might be related to the MacOS update.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
No response
What is the output of
bazel info release?No response
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD?No response
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: