Skip to content

speedup: start the k3s E2E rows without waiting for the deb and RPM packages #5862

Open

Description

@matthewgrossman

User Story

As a contributor waiting on Branch E2E, I want the k3s rows to start as soon as their own inputs are built, so that the rows that end every run start 8–10 minutes sooner.

Description

All tmachine rows wait for prepare-integration, which waits for the Debian and RPM packages. The deb waits for the VM driver, which waits for every Linux build. In runs 44790695612, 44794801466, 44803364078 and 44803367985, the tmachine rows started at 18–22 min.

The k3s rows don't install the deb or the RPM, yet they are the longest rows (17–27 min) and end every run. Their own inputs (images, CLI, test inputs) are ready by about 10 min. podman-e2e-integration waits the same way.

Proposed change

  • Split the integration inputs so k3s rows get an artifact without the packages, and start them as soon as that is ready.
  • Do the same for any other rows or jobs that don't use the packages.
  • Keep the deb and RPM rows on the current path.

Context

Definition of Done

  • k3s rows no longer wait for build-deb, build-rpm or build-vm-driver-linux.
  • Deb and RPM rows still get the packages.
  • Branch E2E passes, and the PR records before/after start times for the k3s rows and the whole run.

+++ Agent notes

  • prepare-integration needs [pr_metadata, build-binaries-linux, build-images, build-deb, build-rpm, build-tmachine-test-inputs, build-external-drivers] and produces one integration_inputs_artifact_id that e2e-suites.yml downloads for every row.
  • Check what the k3s installer reads from that artifact (tests/tmachine/artifacts.nix, tests/tmachine/config.nix, the k3s playbooks) and whether external drivers matter for k3s rows.
  • The matrix in e2e-suites.yml mixes installers in one call; splitting the call by installer or adding a second inputs artifact are both options.

+++

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 20, 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