Java/proto project fails about bazel-buildfarm HOT 3 CLOSED

(This is a bit of a drive-by since I haven't used buildfarm)
I got this error when experimenting with docker-sandboxing yesterday, and found that the CROSSTOOL added cxx_builtin_include_directory for a gcc/clang version different from the container version.
Example from the bazel-toolchains repo: https://github.com/bazelbuild/bazel-toolchains/blob/master/configs/ubuntu16_04_clang/1.0/bazel_0.14.1/default/CROSSTOOL#L152
In my case, I was able to "just" add/remove lines that point to the headers of the correct version.

from bazel-buildfarm.

This is technically an issue with bazel itself, and one that I've seen crop up in a build of bazel that crossed ubuntu version boundaries. As @RNabel is indicating, your client is perceiving the gcc 5 environment that your workers are using during compilation as depending upon headers that bazel does not believe are enumerated as inputs. Getting these two environments matched will be the bulk of the work required to make this work properly.

from bazel-buildfarm.

Thank you @RNabel and @werkt - upgrading the host OS for the workers indeed solved my problem.

from bazel-buildfarm.