summary refs log tree commit diff
path: root/.github
diff options
context:
space:
mode:
authorkegsay <kegan@matrix.org>2022-02-04 13:04:57 +0000
committerGitHub <noreply@github.com>2022-02-04 13:04:57 +0000
commita3865ed525db76eda31780cf6e03574b53e97e11 (patch)
tree6389d4d0c5853543464cd62edebbe6f77b235a6e /.github
parentStabilise MSC3231 (Token Based Registration) (#11867) (diff)
downloadsynapse-a3865ed525db76eda31780cf6e03574b53e97e11.tar.xz
Run Complement tests sequentially (#11910)
Since #11811 there has been general Complement flakiness around networking.
It seems like tests are hitting the wrong containers. In an effort to diagnose
the cause of this, as well as reduce its impact on this project, set the
parallelsim to 1 (no parallelism) when running tests.

If this fixes the flakiness then this indicates the cause and I can diagnose
this further. If this doesn't fix the flakiness then that implies some kind
of test pollution which also helps to diagnose this further.
Diffstat (limited to '.github')
-rw-r--r--.github/workflows/tests.yml2
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index e0f80aaaa7..c395f3e1c2 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -383,7 +383,7 @@ jobs:
       # Run Complement
       - run: |
           set -o pipefail
-          go test -v -json -tags synapse_blacklist,msc2403 ./tests/... 2>&1 | gotestfmt
+          go test -v -json -p 1 -tags synapse_blacklist,msc2403 ./tests/... 2>&1 | gotestfmt
         shell: bash
         name: Run Complement Tests
         env: