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

test(infra): poll-for-event race fixes + watchdog timeout bump + spec update

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-06-10 15:14:35 -04:00
parent 563e609505
commit 2c924fe6df
4 changed files with 55 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conductor/tracks/rag_phase4_sync_fix_20260610/spec.md
+4 -2
View File
@@ -4,9 +4,11 @@
This track fixes a pre-existing RAG test failure that halted the `tier-3-live_gui` batch during the `mma_tier_usage_reset_fix_20260610` verification run on 2026-06-10.
**The bug:** `tests/test_rag_phase4_final_verify.py::test_phase4_final_verify` fails because `rag_status` stays at `'idle'` after the test sets `rag_enabled=True`, `rag_source='chroma'`, `rag_emb_provider='local'` via the Hook API. The test polls for `rag_status == 'ready'` for 50 seconds (100 × 0.5s) and never sees it.
**The original bug (FIXED):** `tests/test_rag_phase4_final_verify.py::test_phase4_final_verify` failed with "RAG sync failed. Status: idle" because `_handle_reset_session` set `self.rag_config = None` and the `rag_*` setters check `if self.rag_config:` before doing anything — so the 4 setters fired by the test were all no-ops.
The test was failing before any changes from the `mma_tier_usage_reset_fix_20260610` track. It is a pre-existing fragility in the RAG sync flow that the previous track's batch run exposed.
**Fix:** reset `rag_config` to a fresh `RAGConfig()` default (not None) in `_handle_reset_session`, so the setters can mutate it and trigger the sync.
**Status (post-fix):** RAG sync now reaches `'ready'`; the test fails on a SEPARATE downstream assertion (retrieval order — see "Residual issue" below).
## Reproduction (already verified)