Skip to content

Track transient browser-editor SSH EOF on Firecracker #672

Open

Description

@hbrodin

A scheduled Firecracker integration run had one failure in the Ubuntu 24.04 workspace shard while installing code-server:

  • The editor download reached about 219 MB, then its SSH status stream closed without a structured guest failure report.
  • The VM remained usable and the remaining workspace checks passed: 173 passed, 1 failed, 6 skipped.
  • The same fresh-install scenario passed in the Ubuntu 26.04 matrix job.
  • A targeted rerun performed another fresh download/install and passed the full shard: 174 passed, 0 failed, 6 skipped.

Failed run and successful rerun: https://github.com/trailofbits/coop/actions/runs/42952333766

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.

Activity

  1. hbrodin commented on Nov 11, 2026

    @hbrodin
    CollaboratorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions