From 1262b91782c4f5e91196c444d50908e92f7814f6 Mon Sep 17 00:00:00 2001
From: "Michael J. Sullivan" <sully@msully.net>
Date: Wed, 15 Jan 2025 13:59:24 -0800
Subject: [PATCH] Drop dump_traceback_later call (#8225)

30 minutes can get hit easily, and I think this might have been causing
crashes in our nightly tests.
See
https://github.com/edgedb/edgedb/actions/runs/12779694201/job/35626124790

I don't fully understand why it would crash though.
---
 edb/tools/test/runner.py | 2 --
 1 file changed, 2 deletions(-)

diff --git a/edb/tools/test/runner.py b/edb/tools/test/runner.py
index 21fd87e380e..b1be0126942 100644
--- a/edb/tools/test/runner.py
+++ b/edb/tools/test/runner.py
@@ -96,8 +96,6 @@ def init_worker(
     global py_random_seed
 
     faulthandler.enable(file=sys.stderr, all_threads=True)
-    # If we're still running after 30 minutes, dump the traceback.
-    faulthandler.dump_traceback_later(30 * 60, file=sys.stderr)
 
     if additional_init:
         additional_init()