We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Describe the bug The test module run for PR bazelbuild/bazel-central-registry#3288 fails on Windows:
C:/b/bk-windows-j20f/bazel-org-repo-root/output/rules_sh-0.5.0/tests/sh_binaries/BUILD.bazel:3:23: Executing genrule //sh_binaries:genrule failed: (Exit 127): bash.exe failed: error executing Genrule command (from target //sh_binaries:genrule) ... /usr/bin/bash: line 1: c:\\b\\3mrahdhj\\execroot\\_main\\bazel-out\\x64_windows-fastbuild\\bin\\sh_binaries\\hello_world.exe.runfiles/_main/sh_binaries/hello_world: No such file or directory
See https://buildkite.com/bazel/bcr-presubmit/builds/9106
To Reproduce Run bazel test ... in tests directory on Windows with Bazel >= 7.3.
bazel test ...
tests
Expected behavior All tests should pass.
Environment
The text was updated successfully, but these errors were encountered:
BISECT for #93
0dfb883
Note, this only happens when using --build_tests_only (which is used by default on BCR tests).
--build_tests_only
I tracked this down to bazelbuild/bazel@282ac62 bazelbuild/bazel@610fe7b
Sorry, something went wrong.
@fmeum do you have an idea how I can fix this? Should I create an issue in bazelbuild/bazel?
Thanks for catching this. Could you file an issue on the Bazel repo? This needs a fix and probably also a point release. I'll dig into why it happens.
avdv
No branches or pull requests
Describe the bug
The test module run for PR bazelbuild/bazel-central-registry#3288 fails on Windows:
See https://buildkite.com/bazel/bcr-presubmit/builds/9106
To Reproduce
Run
bazel test ...
intests
directory on Windows with Bazel >= 7.3.Expected behavior
All tests should pass.
Environment
The text was updated successfully, but these errors were encountered: