Don't run tests with database in parallel.

By default, multiple packages may be tested in parallel in different processes. Passing -p 1 reduces this to one process to prevent test cases in different packages from accessing the same database. Note that t.Parallel() only affects parallelism within one process, i.e. within the tests of one package. Co-authored-by: Alvar Penning <[email protected]>
Icinga · Jul 18, 2024 · 20717c4 · 20717c4
1 parent 642cf6a
commit 20717c4
Showing 1 changed file with 12 additions and 2 deletions.
diff --git a/.github/workflows/tests_with_database.yml b/.github/workflows/tests_with_database.yml
@@ -71,7 +71,12 @@ jobs:
 
       - name: Run tests
         timeout-minutes: 10
-        run: go test -v -timeout 5m ./...
+        # By default, multiple packages may be tested in parallel in different
+        # processes. Passing -p 1 reduces this to one process to prevent test
+        # cases in different packages from accessing the same database. Note
+        # that t.Parallel() only affects parallelism within one process, i.e.
+        # within the tests of one package.
+        run: go test -v -timeout 5m -p 1 ./...
 
   postgresql:
     name: PostgreSQL ${{ matrix.version }}
@@ -125,4 +130,9 @@ jobs:
 
       - name: Run tests
         timeout-minutes: 10
-        run: go test -v -timeout 5m ./...
+        # By default, multiple packages may be tested in parallel in different
+        # processes. Passing -p 1 reduces this to one process to prevent test
+        # cases in different packages from accessing the same database. Note
+        # that t.Parallel() only affects parallelism within one process, i.e.
+        # within the tests of one package.
+        run: go test -v -timeout 5m -p 1 ./...