Every projects on ci.bazel.io are red on Jenkins

[damienmg]

Due to missing runfiles

[damienmg]

I higly suspect 857cda2

This wasn't caught earlier because the JDK7 build breakage was preventing downstream project from being built

[damienmg]

confirmed suspect.

[damienmg]

Broken builds because jenkins cannot show them easily:
http://ci.bazel.io/job/rules_closure/55/
http://ci.bazel.io/job/rules_scala/79/
http://ci.bazel.io/job/skydoc/8/
http://ci.bazel.io/job/TensorFlow/179/
http://ci.bazel.io/job/TensorFlow_Serving/60/
http://ci.bazel.io/job/Tutorial/243/

[kchodorow]

Thanks, on it.

[kchodorow]

Verifying now, but I think this is caused by the SourceManifestAction caching issue, which I've got an LGTM'd CL to fix.

[kchodorow]

Yup, that's it!

Note that this won't fix everything, I think the AppEngine rules are just broken because they assume an empty workspace name. But it should be much better.

[damienmg]

the appengine rules where not broken by that change

[kchodorow]

Well, they should have been. Guess they're not very well tested.

[damienmg]

http://ci.bazel.io/job/skydoc/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/11/console at least one breakage left. ci is still running :(

[damienmg]

TensorFlow tests are still failing :( I need to go home now and probably will be offline. Feel free to push if you have more fixes for that.

[kchodorow]

Happily, the TF failure looks like a flake (it passes for me locally). However, I'm not sure why the other tests are failing, so I'm rolling back. The failing tests are now:

• TF Serving
• SkyDoc - I couldn't actually figure out how to get to this failure.
• Tutorial - android rules are accessing the wrong path.
• rules_rust
• rules_closure