Fabian Meumertzheim
Fabian Meumertzheim
Reopening, I accidentally left the issue reference in the PR description even after you confirmed the error. Something seems to have regressed on master, I will investigate further.
@DavidANeil Nvm, I forgot to mention that path mapping doesn't support the unsandboxed multiplex worker mode used by Java actions (see https://youtu.be/Et1rjb7ixUU?t=1300). Could you try again with `--worker_sandboxing --noexperimental_worker_multiplex`?
What I know is https://github.com/bazelbuild/bazel/pull/19719#issuecomment-1750361465. Feel free to update the title. @hvadehra Has the internal situation regarding sandboxed multiplexed Javac workers changed? Would you accept a PR along the lines...
@wilwell Thanks for the update! Glad to hear that this is at least on the roadmap. In the meantime, what do you think of merging just the JavaBuilder and worker...
@iancha1992 This is actually a separate issue. Could you change the title to `Add multiplex sandboxing support for Java actions`?
I learned that Lars is no longer working in this area, so cc @wilwell as well.
@bazel-io flag
Could you share the contents of the param file passed to `gcc`? And where is `ld` located on your machine?
This part is buggy: ``` -fuse-ld=lld -B/usr/bin ``` Bazel's toolchain forces use of `lld`, but adds the path to `ld` to the search path.
`JavaToolchainInfo` exposes `jacocorunner`, which embeds the JaCoCo runtime part. Maybe you could extract the JaCoCo package from it in an action?