From a2bc85144c3f52b35cba7d275a550f9e5933cf9c Mon Sep 17 00:00:00 2001 From: Sam Kleinman Date: Tue, 9 Aug 2022 08:02:14 -0400 Subject: [PATCH] e2e: fix out of sync configuration (#9199) The v0.34.x tests have been failing (or reporting failures, I don't believe that this is a real failure,) because the CI configuration has been out of sync with itself, likely due to a mistake during backporting configs from the `master` branch. The entire 0.34.x e2e test suite takes 26 minutes to run, plus about 7 minutes to build the docker image. Each split has to build the same docker image, (and is therefore a cap on the amount of parallelism we can get at the moment.) Having more groups, just seems like we'll be burning money building the docker image with no really meaningful difference in throughput. For a nightly test that people don't really wait on, the current latency (time-to-completion) of roughly 19 minutes, isn't causing in friction. --- .github/workflows/e2e-nightly-34x.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/e2e-nightly-34x.yml b/.github/workflows/e2e-nightly-34x.yml index 17dab56b0..124a401f3 100644 --- a/.github/workflows/e2e-nightly-34x.yml +++ b/.github/workflows/e2e-nightly-34x.yml @@ -15,7 +15,7 @@ jobs: strategy: fail-fast: false matrix: - group: ['00', '01', '02', '03', "04"] + group: ['00', '01'] runs-on: ubuntu-latest timeout-minutes: 60 steps: