Skip to content

ci(e2e): finish the Linux VM driver build sooner #5636

Open

Description

@matthewgrossman

User Story

As a contributor waiting on Branch E2E, I want the Linux VM driver build to finish sooner, so that the Debian package, the last input to the tmachine rows, stops trailing the RPM.

Description

After #5530, build-deb runs on a hosted runner and starts as soon as build-vm-driver-linux finishes. In run 44021924417, the deb finished 1.1 minutes after the RPM. That remaining gap is the VM driver build, which also delays every release build.

Where the VM driver job spends its time:

  • It waits for every Linux binary. It only uses the openshell-sandbox, openshell-supervisor and openshell-vm-init artifacts, but needs: build-binaries-linux also waits for the slower gateway legs. In the baseline runs, the gateway finished 1–2 minutes after the supervisor.
  • It queues on the self-hosted pool. It runs on linux-amd64-cpu8/linux-arm64-cpu8. In run 43257220972 it waited 3.6 minutes for a runner, and the deb finished 7.1 minutes after the RPM.
  • Most of the job is compiling the driver. In run 44021924417, setup-nix took ~50 s, compressing the embedded binaries ~30 s, and Build openshell-driver-vm ~160 s. Only the final embedding step needs the downloaded binaries.

Options to evaluate:

  • Depend only on the three binaries the driver embeds, for example by splitting them out of build-binaries-linux or giving them their own reusable workflow call.
  • Start the job alongside build-binaries-linux: set up Nix and compile the driver's dependencies first, then wait for the artifacts and embed them.
  • Move the job to a hosted runner, if the build fits its CPU and disk limits.

Context

Definition of Done

  • build-vm-driver-linux no longer waits for builds it doesn't use, or no longer queues on the self-hosted pool.
  • Release builds still produce the same VM driver and Debian packages.
  • Branch E2E passes, and the PR records before/after times for the VM driver and the deb.

Activity

  1. added
    area:buildCI/CD workflows, releases, build targets, packaging, and artifact publication.
    topic:testingUnit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.
    on Nov 17, 2026
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

    area:buildCI/CD workflows, releases, build targets, packaging, and artifact publication.topic:testingUnit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions