Description of the bug:
When I run bazelisk to load the latest rolling version of bazel to build some code on Windows running on an ARM 64 machine, I see:
pwsh❯ bazel build ...
Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing c:\users\yesudeep\_bazel_yesudeep\dtybepaq\server\jvm.out
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.UnsatisfiedLinkError: 'int com.google.devtools.build.lib.windows.WindowsFileOperations.nativeIsSymlinkOrJunction(java.lang.String, boolean[], java.lang.String[])'
at com.google.devtools.build.lib.windows.WindowsFileOperations.nativeIsSymlinkOrJunction(Native Method)
at com.google.devtools.build.lib.windows.WindowsFileOperations.isSymlinkOrJunction(WindowsFileOperations.java:143)
at com.google.devtools.build.lib.windows.WindowsFileSystem.isSymlinkOrJunction(WindowsFileSystem.java:264)
at com.google.devtools.build.lib.windows.WindowsFileSystem.fileIsSymbolicLink(WindowsFileSystem.java:135)
at com.google.devtools.build.lib.windows.WindowsFileSystem.stat(WindowsFileSystem.java:158)
at com.google.devtools.build.lib.vfs.FileSystem.statNullable(FileSystem.java:511)
at com.google.devtools.build.lib.vfs.FileSystem.readdir(FileSystem.java:632)
at com.google.devtools.build.lib.vfs.Path.readdir(Path.java:268)
at com.google.devtools.build.lib.exec.BinTools.scanDirectoryRecursively(BinTools.java:132)
at com.google.devtools.build.lib.exec.BinTools.forProduction(BinTools.java:80)
at com.google.devtools.build.lib.runtime.BlazeRuntime.newRuntime(BlazeRuntime.java:1299)
at com.google.devtools.build.lib.runtime.BlazeRuntime.serverMain(BlazeRuntime.java:1024)
at com.google.devtools.build.lib.runtime.BlazeRuntime.main(BlazeRuntime.java:769)
at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:96)
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.
Run bazel build ...
Which operating system are you running Bazel on?
Windows 11 arm64
What is the output of bazel info release?
The output is that error.
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 master; 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 matter what bazel subcommand I run, I get the same error.
Description of the bug:
When I run bazelisk to load the latest rolling version of bazel to build some code on Windows running on an ARM 64 machine, I see:
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.
Run
bazel build ...Which operating system are you running Bazel on?
Windows 11 arm64
What is the output of
bazel info release?The output is that error.
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 master; 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 matter what bazel subcommand I run, I get the same error.