-
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
py_test/sh_test pulls in unnecessary java repositories at runtime (0.26) #8575
Comments
This is not specific to Python. I'm able to reproduce it for |
`py_test` tries to download unnecessary dependencies at runtime. We can just as well run it to check the assertion. Upstream issue: bazelbuild/bazel#8575
`py_test` tries to download unnecessary dependencies at runtime. We can just as well run it to check the assertion. Upstream issue: bazelbuild/bazel#8575
The problem is that all Test rules depend on |
Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so. |
Description of the problem / feature request:
Bazel 0.26 tries to download
remote_java_tools_linux
for a trivialBUILD
file using thepy_binary
rule.I’d expect bazel to support its builtin rules without depending on external repositories.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Please see the minimal repro here: https://github.com/Profpatsch/repros/tree/master/bazel-python_binary-downloads-repostitories
Go offline and run the command in the repro.
What operating system are you running Bazel on?
What's the output of
bazel info release
?$ bazel info release
release 0.26.0- (@non-git)
If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
?non-applicable
Have you found anything relevant by searching the web?
nothing here in the issue tracker
The text was updated successfully, but these errors were encountered: