Skip to main content
This guide helps you troubleshoot slow upload issues when building with BuildBuddy.

Common Upload Issues

This error means the bes_timeout flag is likely set to a value that’s not long enough for bazel to finish uploading all build artifacts.

Solution

We recommend using the following flag to increase this upload timeout:
--bes_timeout=600s
These slow uploads should only happen once when artifacts are initially written to the cache, and shouldn’t happen on subsequent builds.
If your build has finished but you’re frequently sitting around waiting for build events to upload - you’re likely in a network constrained environment trying to upload large build artifacts like docker images or large binaries.

Solution for Network Constrained Environments

We recommend running with the flag:
--noremote_upload_local_results
This will upload build, test, and profiling logs - but not the larger build artifacts that can take much longer to upload.

Quick Reference

Increase Timeout

Use --bes_timeout=600s to allow more time for uploads

Skip Large Artifacts

Use --noremote_upload_local_results to skip uploading large build artifacts

Build docs developers (and LLMs) love