Skip to content
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

Fails on Bazel's CI for Bazel >= 7.3 on Windows #93

Open
avdv opened this issue Dec 2, 2024 · 3 comments
Open

Fails on Bazel's CI for Bazel >= 7.3 on Windows #93

avdv opened this issue Dec 2, 2024 · 3 comments
Assignees

Comments

@avdv
Copy link
Member

avdv commented Dec 2, 2024

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.

Expected behavior
All tests should pass.

Environment

  • OS name + version: Windows
  • Bazel version: 7.3.0 - 7.4.1
  • Version of the rules: 0.5.0
@avdv avdv added the type: bug label Dec 2, 2024
@avdv avdv self-assigned this Dec 2, 2024
avdv added a commit that referenced this issue Dec 2, 2024
@avdv
Copy link
Member Author

avdv commented Dec 3, 2024

Note, this only happens when using --build_tests_only (which is used by default on BCR tests).

I tracked this down to bazelbuild/bazel@282ac62 bazelbuild/bazel@610fe7b

@avdv
Copy link
Member Author

avdv commented Dec 3, 2024

@fmeum do you have an idea how I can fix this? Should I create an issue in bazelbuild/bazel?

@fmeum
Copy link

fmeum commented Dec 3, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants