A simulated run that fails in the image self-check leaves no log of why #285
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What happens
Deploy run #243 (
8c527d6) failed its image self-check: thegit-flowsimulated run reportedthe runner failed: RemoteProtocolError: Server disconnected without sending a responseat 0.0 s. That is the scenario's own osfd closing the connection on the firstPOST /api/runs, so the process most likely died mid-request. The self-check keeps noosfd.logfor a failed scenario, so why can't be told. The same commit passed the smoke set locally (7 of 7), and a re-dispatched deploy passed. An hour earlier, the PR's CI on the same runner had seven unrelated tests 3 to 10 times over their time limits.Fix
Done when
A failed self-check scenario's job log shows why its osfd stopped.
Shipped in PR #297 (
1d98b25). A scenario whose osfd drops a request fails with "osfd hung up on POST /api/runs: RemoteProtocolError: …", and keeps the last 40 lines of its osfd log.python -m osf.sim --logsprints them under the scenario, and the image self-check passes--logs.The production deploy's self-check passed this time, so the new output had nothing to show; the test drives a scenario whose osfd hangs up on
POST /api/runsand checks the failure line and the 40-line log tail.