diff options
author | pcloudy <pcloudy@google.com> | 2017-11-15 07:11:08 -0800 |
---|---|---|
committer | Copybara-Service <copybara-piper@google.com> | 2017-11-15 07:19:40 -0800 |
commit | 275ae45b1228bdd0f912c4fbd634b29ba4180383 (patch) | |
tree | 6264b6aa3eb23a451a0b3c41935a7197a8815bfd /src/test/java/com/google/devtools/common | |
parent | 84943fc8f84fef04cf0a7b7fe7f0abea1e1497f2 (diff) |
Automated rollback of commit 4869c4e17d5b1410070a1570f3244148d8f97b5d.
*** Reason for rollback ***
Causing Bazel server to crash when running bazel clean --expunge
https://github.com/bazelbuild/bazel/issues/3956
*** Original change description ***
Delayed rollforward of commit 8fb311b4dced234b2f799c16c7d08148619f4087.
This was rolled back due to Tensorflow breakage but the patch I exported to gerrit (https://bazel-review.googlesource.com/c/bazel/+/18590) passed Tensorflow (https://ci.bazel.io/job/bazel/job/presubmit/52/Downstream_projects/). Confirmed with jcater@ that the "newly failing" projects in the Global Tests are known issues. I think we can check this in now.
Additionally I had attempted to reproduce any tensorflow issues with this by building and testing Tensor...
***
ROLLBACK_OF=172361085
RELNOTES:None
PiperOrigin-RevId: 175821671
Diffstat (limited to 'src/test/java/com/google/devtools/common')
0 files changed, 0 insertions, 0 deletions