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

test(live_workflow): bump project switch wait timeout 30s -> 120s

Browse Source 
The 30s wait_for_project_switch timeout was an excessive constraint.
In batch context, prior sims' AI discussion turn workers saturate the
8-worker io_pool, queueing this switch for tens of seconds. The other
defensive waits in the test (warmup 60s, prior switch 60s) already use
60s+, so 30s was the inconsistent outlier.

User confirmed: 'I think not completing in 30s is an excessive constraint
if thats whats going on.'

Verification:
- test_full_live_workflow isolation: 11.69s PASS
- 7-test batch (test_full_live_workflow + 4 extended sims + 2 markdown): 85.83s PASS
This commit is contained in:
Edward R. Gonzalez
2026-06-08 18:14:18 -04:00
parent 87d7c5bff2
commit c9a991bbb8
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/test_live_workflow.py
+3 -1
View File
@@ -88,7 +88,9 @@ def test_full_live_workflow(live_gui) -> None:
# Wait for project switch to complete (deterministic, condition-based). # Wait for project switch to complete (deterministic, condition-based).
# Replaces the prior 10x1s blind poll of derived state. # Replaces the prior 10x1s blind poll of derived state.
status = client.wait_for_project_switch(expected_path=temp_project_path, timeout=30.0) # Timeout is 120s: in batch context, prior sims' AI discussion turn workers
# can saturate the 8-worker io_pool, queueing this switch for tens of seconds.
status = client.wait_for_project_switch(expected_path=temp_project_path, timeout=120.0)
assert not status.get("timeout"), ( assert not status.get("timeout"), (
f"Project switch did not complete in 30s. Last status: {status}" f"Project switch did not complete in 30s. Last status: {status}"
) )