fix(harness): un-xfail peer-discovery-404 replay (Fixes #2865) #2870
Reference in New Issue
Block a user
Delete Branch "fix/2865-peer-discovery-404-replay"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The
canary-smoke-peer-discovery-404replay was xfailing (#2865) because its parse half assumed a core-localworkspace/a2a_client.py, but the diagnostic helper actually lives in the workspace-runtime package (molecule_runtime.a2a_client).Fix
Retire the parse half from the harness replay. The wire-404 assertion already passes, and the diagnostic-helper behavior is already covered by the workspace-runtime unit tests.
__XFAIL__early-exit guard./registry/<unregistered>/peersreturns HTTP 404.Verification
bash -n tests/harness/replays/peer-discovery-404.shpasses.Fixes #2865
APPROVED on head
57a7f3a9.Verified the actual Harness Replays job 501539 on this head: peer-discovery-404 ran, generated an unregistered workspace id, queried
/registry/<id>/peers, received HTTP 404, printedPASS: peer-discovery wire returns 404 for an unregistered workspace, and the replay suite finished8 passed, 0 failed.The script change is correctly scoped to the one replay file: it removes the stale
__XFAIL__early exit and the obsolete core-local parse branch, while preserving the wire assertion as live coverage. Retiring the parse half is sound because the diagnostic helper lives in workspace-runtime, not core; runtime already has unit coverage aroundmolecule_runtime.a2a_client.get_peers_with_diagnostic, including the 404 diagnostic path asserting an explicit source id is used and the diagnostic says the workspace is not registered.CI is green on the exact head, including CI/all-required and Harness Replays.