ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

chore(test): double smart_watchdog timeout from 300s to 600s for tier-3

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-06-09 18:37:34 -04:00
parent 3b0e63124a
commit c3af1b8a2e
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/conftest.py
+3 -3
View File
@@ -165,7 +165,7 @@ def _check_required_test_dependencies() -> None:
raise pytest.UsageError(msg) raise pytest.UsageError(msg)
def _smart_watchdog_exit() -> None: def _smart_watchdog_exit() -> None:
if not _pytest_finished_event.wait(timeout=300.0): if not _pytest_finished_event.wait(timeout=600.0):
os._exit(2) os._exit(2)
import time import time
time.sleep(5.0) time.sleep(5.0)
@@ -177,11 +177,11 @@ def _unconditional_watchdog_exit() -> None:
"""Hard fail-safe: also signal-based, but with a much longer """Hard fail-safe: also signal-based, but with a much longer
timeout than the smart watchdog. timeout than the smart watchdog.
The smart watchdog (above) uses 300s. This sledgehammer waits The smart watchdog (above) uses 600s. This sledgehammer waits
900s (15 minutes) for the same signal, so a long-running test 900s (15 minutes) for the same signal, so a long-running test
can take up to 15 minutes before we declare it a hang. The can take up to 15 minutes before we declare it a hang. The
only case this catches that the smart doesn't: pytest finishes only case this catches that the smart doesn't: pytest finishes
but the test session is so long the smart's 300s expires first. but the test session is so long the smart's 600s expires first.
In that case we still want the runner to move on. In that case we still want the runner to move on.
If the signal never fires (true hang), os._exit(2) so the runner If the signal never fires (true hang), os._exit(2) so the runner