-
Notifications
You must be signed in to change notification settings - Fork 283
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
enhance Bazel easyblock to avoid writing to $HOME in sanity check #2756
enhance Bazel easyblock to avoid writing to $HOME in sanity check #2756
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Test report by @ocaisa Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (2 easyconfigs in total) |
Test report by @ocaisa Overview of tested easyconfigs (in order)
During handling of the above exception, another exception occurred: Traceback (most recent call last):
During handling of the above exception, another exception occurred: Traceback (most recent call last): Build succeeded for 0 out of 2 (2 easyconfigs in total) |
|
I don't really see a way to avoid this... I'm also surprised your |
Test report by @ocaisa (sanity check run) Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (2 easyconfigs in total) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Test report by @ocaisa Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (2 easyconfigs in total) |
(created using
eb --new-pr
)Detected by a readonly file
$HOME/.cache/bazel
in Bazel 1+ ECs:The approach here uses a kind of "cached" property to avoid changing more code than required and always have access to
self.output_user_root
even in sanity checks with--module-only
or--sanity-check-only