-
Notifications
You must be signed in to change notification settings - Fork 200
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
Java/proto project fails #199
Comments
(This is a bit of a drive-by since I haven't used 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. |
I'm trying to get build-farm running on Ubuntu.
I successfully installed all required dependencies and Bazel 0.19.2, cloned the repo and started server and worker with the example configuration, each in its own screen.
This failed until I added a wrapper script exporting BAZEL_SH and JAVA_HOME.
Now both start up.
As demonstrated by the local build of build-farm itself, I can build java projects.
Starting it from a remote machine, I get loads of errors like this:
With logging enabled, all looks fine to me on both server and worker:
The server has lots of log lines like these:
The worker log lines come in blocks and look like this:
I'm at a loss and I'd really love to get this running. If you need more info, I'll give my best to assist.
The text was updated successfully, but these errors were encountered: