From f8fd8648eca2f5838ff0174d5eb96850d0982343 Mon Sep 17 00:00:00 2001 From: josh11b Date: Fri, 15 Sep 2023 14:20:06 -0700 Subject: [PATCH] Reduce bazel job limit to try to avoid IOExceptions (#3240) Issue reported in [#infra on Discord](https://discord.com/channels/655572317891461132/707150492370862090/1152031995740827718). --- .github/workflows/tests.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/tests.yaml b/.github/workflows/tests.yaml index f436873bf4d1..b59db69f8c87 100644 --- a/.github/workflows/tests.yaml +++ b/.github/workflows/tests.yaml @@ -182,7 +182,11 @@ jobs: # There is a new effort (yay!) but until then it seems worth using the # workaround of a high jobs value. The biggest downside (increased # heap usage) seems like it isn't currently a big loss for our builds. - build --jobs=50 + # + # Higher values like 50 have led to CI failures with network errors + # and IOExceptions, see + # https://discord.com/channels/655572317891461132/707150492370862090/1151605725576056934 + build --jobs=32 # General build options. build --verbose_failures