-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Enable Bazel remote caching on more/most continuous/experimental builds by default #8997
Comments
Per f2f, can close when all PR jobs can use caching (including debug / sanitizer): Remaining bits:
At present, we save some budget, but dev experience is still a little painful due to having to wait for presently non-cached builds (debug, sanitizer). Will see how things go for the next month to see how budget + dev experience goes. |
FYI At TRI I'm experimenting with turning on Fission for Anzu. Fission should work fine on Bionic at least, and it's on the order of 5x reduction in debug build footprints (80% smaller). I think upstream bazelbuild/bazel#6606 would enable Fission by default on all of our platforms, but it's stalled in review. I wonder if we could help nudge that along, or if there is a 30-line patch to Drake that could have the same effect (declare our own crosstool, but delegate most of it to upstream local_cc). Fission may also help with #9952. |
If it's truly mac that is holding them up, I could probably run with it, since I already worked with that code, but not convinced it is. That PR is on the wrong side of bazelbuild/bazel#7320 so would need some work to bring it up to date in any case. |
(My understanding is that debug fission with |
bazelbuild/bazel#327 is relevant for Mac. |
Fair enough. Sounds like the low-hanging fruit might be a bionic debug build that is included in the pre-merge set, depending on the crosstool hijinks that we'd need. How about I take a bit more time to see how Anzu fares once I turn this on there, and then we can revisit the question for Drake? |
Sounds good. |
I just looked at the most recent PR, and all of the jobs appear to be using the remote cache. |
A tracking issue for the above. More relevant when bionic support causes the number of jobs to increase more than our CI budget can handle.
FYI @EricCousineau-TRI.
The text was updated successfully, but these errors were encountered: