Adversarial editor restart timeout aborts remaining probes and hangs cleanup #959

Open
opened 2026-10-02 23:04:26 +00:00 by kayg · 0 comments
Owner

Merge-round-7a (#427), round 4: the editor probe reports editor findings=10 seed=25608414 historySeeds=25608414. The restart coordinator reports timed out waiting for restart-ready-3 after 6000 polls at 0.1s each. Five editor operations timed out, followed by five Note creation failures with HTTP 502 after cleanup began.

The unguarded restart barrier in tests/adversarial/run.sh exits the set -e runner before the remaining robustness phases. Its EXIT cleanup then waits without a deadline for the server. More than ten minutes later bash remained in do_wait and the server remained alive; this job terminated that server to release cleanup.

Bound restart failures and cleanup, preserve diagnostics, and let remaining independent probes run. Investigate the editor operations separately from the 502 responses after shutdown. This round does not establish complete robustness coverage and is not deploy-ready.

Merge-round-7a (#427), round 4: the editor probe reports `editor findings=10 seed=25608414 historySeeds=25608414`. The restart coordinator reports `timed out waiting for restart-ready-3 after 6000 polls at 0.1s each`. Five editor operations timed out, followed by five Note creation failures with HTTP 502 after cleanup began. The unguarded restart barrier in tests/adversarial/run.sh exits the set -e runner before the remaining robustness phases. Its EXIT cleanup then waits without a deadline for the server. More than ten minutes later bash remained in do_wait and the server remained alive; this job terminated that server to release cleanup. Bound restart failures and cleanup, preserve diagnostics, and let remaining independent probes run. Investigate the editor operations separately from the 502 responses after shutdown. This round does not establish complete robustness coverage and is not deploy-ready.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#959
No description provided.