-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Unresolved symlink to absolute path in remote action outputs is not supported #16290
Comments
While we're at it, we should also remove the limitation in https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/remote/RemoteActionFileSystem.java;l=222;drc=79b5b5ddaa3919db48b9143e0afdd4d2cddfdb74 (which AIUI would only apply when a remotely produced declare_symlink is an input to a local action). |
The tests don't currently pass due to bazelbuild#16290 and bazelbuild#16289. Making them pass might be considered a blocker for bazelbuild#10298 (declaring unresolved symlinks stable).
I'm not too worried about I think what's more important than fixing the mock local executor is exercising this functionality with the real RBE so #16289 should not be a blocker for this. It would be nice, but I could live without it. |
While this feature is listed as experimental, I can speak for the community and say many, many projects depend on it. |
Actually, it's not experimental anymore: https://bazel.build/reference/command-line-reference#flag--remote_download_outputs |
@brentleyjones that's unfortunate, I didn't realize we promoted that flag to production, thanks for pointing it out |
|
Fixes bazelbuild#16290. PiperOrigin-RevId: 478048404 Change-Id: Ibc5b7f681a520dab6945cb18d976440c9f2e62a7
When a remote action produces an undeclared symlink (i.e., a ctx.actions.declare_symlink) pointing to an absolute path, an exception is thrown here: https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java;l=745;drc=bce7db055dd702e8a101f975f8585e0dfeb18a67
We will also have to fix #16289 before adding a regression test for this issue.
This issue may be a blocker for #10298.
Note that this is separate from #13355, which concerns any kind of symlink in action outputs (resolved or unresolved, relative or absolute, dangling or non-dangling) and only applies when building without the bytes.
The text was updated successfully, but these errors were encountered: