-
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
TensorFlow job in Bazel CI is red but only in Ubuntu 14.04 #4928
Comments
This is due to a recent change to remote caching, where we no longer can cache actions that generate symlinks as outputs. I ll take a look. |
This is a regression, so it will be a release blocker for 0.13.0, but not for 0.12.0 because it's cut before the breaking change. |
TF is back to green today (https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/180) but we still need to investigate what's going on here. |
There's a similar issue with rules_typescript: https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/188#6b1ff1cb-296d-41ad-9743-2346d618001f |
TF job is red for both 14.04 and 16.04 now, with a different error.
14.04: https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/197#32044fa3-fa5f-49ac-b157-6e59b8e8df04 |
TF_serving has updated their TF commit hash, but now they're running into the
14.04: https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/197#5a04d42a-f730-4670-9852-7e763d9ef12e |
Ping @buchgr |
Any progress on this? @buchgr |
I have rolled back |
Thanks, I'll cherry-pick it! |
@jin Is there any way to solve the build problem of "python_api_gen failed" on 14.04? |
@arthur309 sorry, I don't know what you're referring to. Is that error related to the remote execution issue in this thread? |
This issue has been resolved by fa36d2f |
The TensorFlow job is failing with:
Looks like a remote execution issue, assigning to @buchgr to diagnose.
Full log in: https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/179#415760a7-1156-4b75-897e-c2ed29db585a
The text was updated successfully, but these errors were encountered: