supply flag for no warning when output base is an nfs mount #5897 - GitHub WARNING: Output base ' bazel-nfs-volume outputs' is on NFS This may lead to surprising failures and undetermined behavior A flag that could request to supress this warning would allow us to solve this Feature requests: what underlying problem are you trying to solve with this feature? To allow developing from the IDE on a mac OSx, with bazel
Using Bazel with output-base on a Shared Filesystem - Google Groups Can you just set --output_base to set the output base to a tmp dir or some other non-NFS directory? Your workspace can still be on NFS but the Bazel cache has to be on non-NFS part You received this message because you are subscribed to the Google Groups "bazel-discuss" group
How to change location of the bazel caching area? Stack Overflow for Teams Where developers technologists share private knowledge with coworkers; Advertising Reach devs technologists worldwide about your product, service or employer brand; Knowledge Solutions Data licensing offering for businesses to build and improve AI tools and models; Labs The future of collective knowledge sharing; About the company Visit the blog
How to install bazel on NFS · Issue #2042 · bazelbuild bazel This may lead to surprising failures and undetermined behavior [bazel release 0 4 0] and the subsequent compile of tensroflow also failed If possible, provide a minimal example to reproduce the problem: Environment info Operating System: Linux gs07 3 16 0-4-amd64 #1 SMP Debian 3 16 7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU Linux Bazel
How to force Bazel to set libraries path to a desired one? Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question Provide details and share your research! But avoid … Asking for help, clarification, or responding to other answers
Error while building tensorflow 0. 11. 0 - cache (directory not empty) NFS mount point are known to be problematic Use --output_base to direct the cache dir of bazel out of the NFS mount point This is a known issue on Windows and @meteorcloudy is working on fixing it IIUC Anyway rm the bazel cache should fix the issue all the time
Change of --output_base causes subsequent builds to fail #10653 When we issue second build command with the different output_base Bazel is smart enough to realize that and spawn second build server process, but unfortunately that stale bazel-<workspace_name> symlink still stays and points inside the old output_base which seems to confuse Bazel