Skip to content

speedup: build the e2e test binaries once per run #5864

Open

Description

@matthewgrossman

User Story

As a contributor waiting on Branch E2E, I want the e2e test binaries built once per run, so that about 14 jobs stop compiling the same Rust tests for 1.4–4.5 minutes each.

Description

Jobs that run directly on the runner (docker-e2e, podman-e2e, vm-e2e, kubernetes-e2e and friends) build the e2e/rust tests and some tests/suites/features tests with cargo test in each job. In run 44803367985, that compile took 1.4–4.5 min per job, in about 14 jobs. kubernetes-e2e compiles twice, for about 3.9–4.5 min.

Conformance already avoids this: build-conformance builds the program once and jobs download it.

Proposed change

  • Build the test binaries these jobs run once per run, for example as a nextest archive per target, in a job beside build-conformance.
  • Run them from the archive in each job, with no Rust toolchain build step.

This saves runner time now. It shortens the whole run only once kubernetes-e2e stops being near the end, which depends on the conformance changes under #5281. Many of these lanes will retire as tests move to testkit (#5297), so keep the change small.

Context

Definition of Done

  • Jobs that run on the runner no longer compile Rust tests.
  • The tests and filters each job runs are unchanged.
  • Branch E2E passes, and the PR records before/after times for the affected jobs.

+++ Agent notes

  • Compile times from logs of run 44803367985: first "Compiling" to last "Finished test profile" line per job.
  • e2e-kubernetes.sh runs cargo test --locked --manifest-path tests/suites/features/Cargo.toml twice (lines ~108 and ~119) and then cargo nextest run --profile e2e-kubernetes.
  • arm64 jobs (docker-e2e runs on ubuntu-24.04-arm) need an aarch64 archive.

+++

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