summaryrefslogtreecommitdiffstats
path: root/packages/meshbay-hub/tests/harness/layout_probe.py
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-09-08 13:21:02 +0200
committerChristophe Besson <cbesson@gmail.com>2026-09-08 13:21:02 +0200
commit79520f5f2f9a38ef719fca4dc0f95b001b477e38 (patch)
treebff43acf1903aeea806a3e983f4be6f29cd2372a /packages/meshbay-hub/tests/harness/layout_probe.py
parentbb8aad22c4d41dd1b89c85c8d46878a31a9530e5 (diff)
downloadmeshbay-79520f5f2f9a38ef719fca4dc0f95b001b477e38.tar.gz
test(hub): stop the Chrome profile cleanup racing its own children
`terminate()` signals the parent only. Chrome's zygote, renderer and gpu children outlive it by a moment and go on writing into the profile, so rmtree walked a directory that gained a file between its readdir and its rmdir and raised "Directory not empty". The probe exited non-zero, and every test in the file errored at setup — intermittently, roughly one run in three, for a reason nowhere near the chat code they were testing. TemporaryDirectory(ignore_cleanup_errors=True) in all four probes that own a profile: a few bytes left in a throwaway directory are harmless, failing the run is not. `proc.wait()` after `kill()` was also missing — a killed process still has to be reaped. layout_probe.py never cleaned up at all (mkdtemp, no removal) and never waited for Chrome; it leaked a profile into /tmp on every run. Ten consecutive runs of test_chat_send.py are clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HCGdheDLxGReuKHga3BtST
Diffstat (limited to 'packages/meshbay-hub/tests/harness/layout_probe.py')
-rw-r--r--packages/meshbay-hub/tests/harness/layout_probe.py12
1 files changed, 11 insertions, 1 deletions
diff --git a/packages/meshbay-hub/tests/harness/layout_probe.py b/packages/meshbay-hub/tests/harness/layout_probe.py
index 530b3f0..65b3083 100644
--- a/packages/meshbay-hub/tests/harness/layout_probe.py
+++ b/packages/meshbay-hub/tests/harness/layout_probe.py
@@ -19,6 +19,7 @@ single pass. Launching Chrome per width put three minutes on the test suite.
"""
import http.server
import json
+import shutil
import socketserver
import subprocess
import sys
@@ -118,16 +119,25 @@ def main() -> int:
srv = S(("127.0.0.1", PORT), H)
threading.Thread(target=srv.serve_forever, daemon=True).start()
+ # mkdtemp left a Chrome profile in /tmp on every run, for ever, and nothing
+ # waited for Chrome to exit. Same cleanup rule as the other probes.
+ profile = tempfile.mkdtemp(prefix="chrome-layout-")
chrome = subprocess.Popen([
"google-chrome", "--headless=new", "--no-sandbox",
"--window-size=1000,900",
- "--user-data-dir=" + tempfile.mkdtemp(prefix="chrome-layout-"),
+ "--user-data-dir=" + profile,
f"http://127.0.0.1:{PORT}/",
], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
deadline = time.time() + 45
while time.time() < deadline and not RECORDS:
time.sleep(0.2)
chrome.terminate()
+ try:
+ chrome.wait(timeout=10)
+ except subprocess.TimeoutExpired:
+ chrome.kill()
+ chrome.wait()
+ shutil.rmtree(profile, ignore_errors=True)
srv.shutdown()
if not RECORDS:
print(json.dumps({"error": "no measurement"}))