Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

chore(tasks): run each follow-up test on its own event loop (#124750)

Julian Bez2539b2b34816
diff --git a/products/tasks/backend/temporal/process_task/tests/test_followup.py b/products/tasks/backend/temporal/process_task/tests/test_followup.py
index 5630ebe8cb24..11f71569739e 100644
--- a/products/tasks/backend/temporal/process_task/tests/test_followup.py
+++ b/products/tasks/backend/temporal/process_task/tests/test_followup.py
@@ -139,7 +139,9 @@ def _mock_cleanup(_input) -> None:
pass
-pytestmark = [pytest.mark.asyncio, pytest.mark.django_db]
+# A timed-out test leaves its coroutine pending on a shared loop, and it would keep writing to the
+# module-level recorders while the next test runs. A loop per test cancels it at teardown.
+pytestmark = [pytest.mark.asyncio(loop_scope="function"), pytest.mark.django_db]
class TestFollowupDeliveryFailure: