-
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
Gracefully handle output symlinks with BwoB #18075
Conversation
@meteorcloudy I assume that this would fix a breakage in rules_go caused by bazelbuild/continuous-integration#1579: https://buildkite.com/bazel/rules-go-golang/builds/5049#018777f3-a4a6-4396-aecc-a7abe4de7ae8/256-294 @coeuvre Could you review this? |
cc @tjgq |
8cc1a74
to
eff963a
Compare
@bazel-io flag |
eff963a
to
180927a
Compare
If an action creates output symlinks, `--remote_download_minimal` now falls back to downloading all its outputs rather than failing with an exception, which most of the time led to a broken build.
180927a
to
0c7c67a
Compare
@coeuvre I fixed the test on Windows (by skipping it), but |
Can you do something similar to |
@tjgq I added a warning and updated the test. |
@bazel-io fork 6.2.0 |
If an action creates output symlinks, `--remote_download_minimal` now falls back to downloading all its outputs rather than failing with an exception, which most of the time led to a broken build. Closes #18075. PiperOrigin-RevId: 524264497 Change-Id: Id0dc77baf1f2c7c54553cf4d7f2d52ce889d1b8b Co-authored-by: Fabian Meumertzheim <[email protected]>
If an action creates output symlinks, `--remote_download_minimal` now falls back to downloading all its outputs rather than failing with an exception, which most of the time led to a broken build. Closes bazelbuild#18075. PiperOrigin-RevId: 524264497 Change-Id: Id0dc77baf1f2c7c54553cf4d7f2d52ce889d1b8b
If an action creates output symlinks,
--remote_download_minimal
now falls back to downloading all its outputs rather than failing with an exception, which most of the time led to a broken build.