Description of the bug:
Likely culprit is a54a393
cc @c-mita
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.
//src/test/shell/bazel/bazel_coverage_java_test.sh and friends no longer pick up changes to java_tools
Hardcoding RULES_JAVA_REPO_NAME to "rules_java~" gets the overrides working again.
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 HEAD ?
No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
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
Description of the bug:
Likely culprit is a54a393
cc @c-mita
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.
//src/test/shell/bazel/bazel_coverage_java_test.sh and friends no longer pick up changes to java_tools
Hardcoding RULES_JAVA_REPO_NAME to "rules_java~" gets the overrides working again.
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 HEAD?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
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