You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Track transient browser-editor SSH EOF on Firecracker #672
The lower-level cause cannot be recovered from the retained logs because editor OpenSSH stderr is suppressed and the artifact does not include guest sshd or kernel diagnostics.
If this recurs:
Preserve a sanitized SSH exit reason and enough guest diagnostics to distinguish transport loss, lease cancellation, and process termination.
Check the editor lease path around download completion.
Consider a repeated cold-install regression fixture.
This is a follow-up investigation, not a current release blocker, because the clean targeted rerun passed.
Release preflight follow-up: the same browser-editor failure reproduced once on Lima during the full release suite, after the editor download completed and while guest systemd launch was being reported. The SSH status stream reached EOF without a guest failure report.\n\nThe immediately preceding Lima suite passed the browser-editor matrix, and a fresh full lifecycle shard then passed the complete matrix again (267 passed, 0 failed overall). This widens the intermittent occurrence from Firecracker to both backends; it is not deterministic, but the cross-platform recurrence is useful evidence for the eventual fix.
Activity
hbrodin commentedon Nov 11, 2026
Release preflight follow-up: the same browser-editor failure reproduced once on Lima during the full release suite, after the editor download completed and while guest systemd launch was being reported. The SSH status stream reached EOF without a guest failure report.\n\nThe immediately preceding Lima suite passed the browser-editor matrix, and a fresh full lifecycle shard then passed the complete matrix again (267 passed, 0 failed overall). This widens the intermittent occurrence from Firecracker to both backends; it is not deterministic, but the cross-platform recurrence is useful evidence for the eventual fix.