//src/test/java/com/google/devtools/build/lib/platform:SystemMemoryPressureEventTest started failing pre- and post-submit
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
### 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 release` returns `development 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 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_
Contributor guide
Research direction
Start with src/test/java/com/google/devtools/build/lib/platform/SystemMemoryPressureEventTest and inspect the linked Buildkite failure logs for the Intel Mac behavior. Reproduce the pre- and post-submit failure, then verify that the test passes on the affected Macs without regressing other platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, macos
- Domain
- build-system, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100