-
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
--local_test_jobs causes bazel to ignore local resource limitations #16786
Comments
Here's what it says in the docs: It does document that if 0, local resource limitations will limit the number, which implies that if non-zero they might not, but it's not explicitly stated, and having the cpu:n tags become a no-op isn't so user friendly and contradicts the spec here: https://bazel.build/reference/test-encyclopedia#other-resources |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale. |
I ran into this too. I only figured out what was going on by reading the bazel source code. |
Description of the bug:
I apply a cpu:4 tag to a set of sh_tests that requires 4 cores to run without timing out. When I set
--local_tests_jobs
the tests are dispatched regardless of the requirement.What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run 2 sh_tests that "sleep 10" with a cpu:1000 tag and
--local_tests_jobs=2
on a multicore system and observe that they finish in ~10s total.Which operating system are you running Bazel on?
Rolling debian testing Rodette
What is the output of
bazel info release
?release 5.3.2
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 master; git rev-parse HEAD
?Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
This is related to and motivated by work on #16785 but affects bazel in general and the cpu tag in an undocumented way.
The text was updated successfully, but these errors were encountered: