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? 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
When running a bazel build, the fetch of an external jar and it's build fails with:
ERROR: /home/user/.cache/bazel/_bazel_user/10c9430dffbe74a86264a0142f3f2d37/external/_main~libmatthew_fetch~libmatthew/jar/BUILD:3:12: Extracting interface for jar external/_main~libmatthew_fetch~libmatthew/jar/downloaded.jar failed: (Segmentation fault): ijar failed: error executing JavaIjar command (from target @@_main~libmatthew_fetch~libmatthew//jar:jar) external/remote_java_tools_linux/java_tools/ijar/ijar external/_main~libmatthew_fetch~libmatthew/jar/downloaded.jar ... (remaining 3 arguments skipped) mmap(): I/O error
But when I run from the command line it succeeds:
$ bazel-repo/external/remote_java_tools_linux/java_tools/ijar/ijar bazel-repo/external/_main~libmatthew_fetch~libmatthew/jar/downloaded.jar $ ls bazel-repo/external/_main~libmatthew_fetch~libmatthew/jar/ BUILD downloaded-interface.jar downloaded.jar
I'm running this on a Windows 10 laptop, running VSCode with a dev container, the OS below is in the container.
Java Rules
No response
Linux ead0f6af3b5d 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 GNU/Linux
bazel info release
release 7.4.1-0
development version
(@non-git)
git remote get-url origin; git rev-parse HEAD
The text was updated successfully, but these errors were encountered:
Do you have a self-contained repro? Can you share the jar file it's crashing on?
Sorry, something went wrong.
Sorry, not sure what you mean. But here's the project: libmatthew
Also, the docker image used as the dev container is:
NAME="Alpine Linux" ID=alpine VERSION_ID=3.21.3 PRETTY_NAME="Alpine Linux v3.21"
I was able to workaround this by adding --nouse_ijars
No branches or pull requests
Description of the bug:
When running a bazel build, the fetch of an external jar and it's build fails with:
But when I run from the command line it succeeds:
I'm running this on a Windows 10 laptop, running VSCode with a dev container, the OS below is in the container.
Which category does this issue belong to?
Java Rules
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Linux ead0f6af3b5d 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 GNU/Linux
What is the output of
bazel info release
?release 7.4.1-0
If
bazel info release
returnsdevelopment 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
?If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
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
The text was updated successfully, but these errors were encountered: