mirror of
https://github.com/pyMC-dev/pyMC_Repeater.git
synced 2026-10-30 19:51:59 +01:00
Merge pull request #431 from pfmos/fix/test-suite-self-kill
This commit is contained in:
commit
af21189115
2 files changed
+61
No files matched your search
@@ -0,0 +1,55 @@
|
||||
"""Shared test guards.
|
||||
|
||||
`RepeaterDaemon._shutdown` arms an exit watchdog: a `threading.Timer` that calls
|
||||
`os._exit(0)` once `SHUTDOWN_EXIT_GRACE_S` has elapsed. That is correct in
|
||||
production -- it guarantees SIGTERM is honoured -- but a test that reaches
|
||||
`_shutdown` without patching it leaves a live timer behind. When it fires, five
|
||||
seconds later, it takes the whole pytest process down **with status 0**, part
|
||||
way through an unrelated test.
|
||||
|
||||
The damage is that it looks like success: pytest exits 0 with no summary line
|
||||
and a truncated progress bar, so CI reports green on a run that never finished
|
||||
and any failure after that point is invisible. The test blamed in the output is
|
||||
whichever happened to be running when the timer fired, so it moves between runs
|
||||
and does not point at the cause.
|
||||
|
||||
The autouse fixture below fails the *responsible* test instead, at the moment it
|
||||
leaks the timer.
|
||||
"""
|
||||
import threading
|
||||
|
||||
import pytest
|
||||
|
||||
_WATCHDOG_NAME = "shutdown-watchdog"
|
||||
|
||||
|
||||
def _live_watchdogs():
|
||||
return [t for t in threading.enumerate() if t.name == _WATCHDOG_NAME and t.is_alive()]
|
||||
|
||||
|
||||
@pytest.fixture(autouse=True)
|
||||
def no_leaked_exit_watchdog():
|
||||
"""Fail any test that leaves a live shutdown-exit watchdog behind.
|
||||
|
||||
Patch it out when the code under test reaches `_shutdown`:
|
||||
|
||||
with patch.object(daemon, "_arm_exit_watchdog"):
|
||||
await daemon.run()
|
||||
|
||||
or, when the watchdog itself is what you are testing, keep the grace short
|
||||
and assert on a patched `repeater.main.os._exit` before the test returns.
|
||||
"""
|
||||
yield
|
||||
|
||||
leaked = _live_watchdogs()
|
||||
for timer in leaked:
|
||||
timer.cancel()
|
||||
|
||||
if leaked:
|
||||
pytest.fail(
|
||||
"test left %d live '%s' timer(s) running. Each one calls os._exit(0) "
|
||||
"when it fires and will kill the pytest process mid-run, with exit "
|
||||
"status 0 and no summary. Patch _arm_exit_watchdog for this test."
|
||||
% (len(leaked), _WATCHDOG_NAME),
|
||||
pytrace=False,
|
||||
)
|
||||
@@ -76,6 +76,12 @@ async def test_run_starts_http_and_handles_dispatcher_cancelled_gracefully():
|
||||
patch("asyncio.get_running_loop", return_value=fake_loop_for_signals),
|
||||
patch("repeater.main.HTTPStatsServer", return_value=fake_http_instance),
|
||||
patch("os.path.exists", return_value=False),
|
||||
# run()'s finally reaches _shutdown(), which arms the real exit
|
||||
# watchdog: a threading.Timer that calls os._exit(0) after
|
||||
# SHUTDOWN_EXIT_GRACE_S (5 s). It would fire long after this test
|
||||
# returns and take the whole pytest process down. Same guard the
|
||||
# shutdown tests in test_main_py_coverage.py already use.
|
||||
patch.object(daemon, "_arm_exit_watchdog"),
|
||||
):
|
||||
await daemon.run()
|
||||
|
||||
|
||||
Reference in new issue
Block a user