Quit (timeout) Python test suite on suspected deadlock

Author: Qqwy

justfile

@@ -40,14 +40,15 @@ test-unit *TEST_ARGS:
   cargo nextest run {{TEST_ARGS}}
 
 # Python integration test suite. Args are forwarded to pytest
+# We run the command with 'timeout 10' to kill pytest if a deadlock were to happen
 [group('test')]
 test-integration *TEST_ARGS: build-bin build-python
   #!/usr/bin/env bash
   set -euxo pipefail
   cd libs/opsqueue_python
   source "./.setup_local_venv.sh"
 
-  pytest --color=yes {{TEST_ARGS}}
+  timeout 30 pytest --color=yes {{TEST_ARGS}}
 
 # Python integration test suite, using artefacts built through Nix. Args are forwarded to pytest
 [group('nix')]

libs/opsqueue_python/pyproject.toml

@@ -52,10 +52,13 @@ test = [
     "pytest==8.3.3",
     "pytest-random-order==1.1.1",
     "pytest-parallel==0.1.1",
+    "pytest-timeout==2.4.0",
     "py==1.11.0", # Needs to be manually specified because of this issue: https://github.com/kevlened/pytest-parallel/issues/118
 ]
 
 [tool.pytest.ini_options]
 # We ensure tests never rely on global state,
 # by running them in a random order, and in parallel:
 addopts = "--random-order --workers=auto"
+# Individual tests should be very fast. If they take longer, this indicates a deadlock
+timeout=20