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
Commit bd8184a
Browse filesBrowse the repository at this point in the historyBrowse files
ci(tests): run the conformance lanes through the test runner
conformance-integration in Branch E2E, Release Dev, and Release
Qualification now runs the cpu-tests plan through e2e-suites.yml, one
job per amd64 environment, replacing the tmachine CLI conformance run.
A matrix entry can name an environment to run on its own. The separate
advisory e2e-suites job is removed.
Signed-off-by: Evan Lezar <[email protected]>
Copy file name to clipboardExpand all lines: CI.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,12 +156,16 @@ retain the binary installer because their fixtures configure its system service,
156
156
local HTTP gateway, and CLI path. The manual Integration Tests workflow defaults
157
157
to the package installers and downloads the packages selected by its matrix.
158
158
159
-
Core integration qualification also runs the SDK-driven e2e suites
160
-
(`e2e-suites.yml`) on the same prepared inputs. Each matrix entry pairs a plan
161
-
from `tests/plans/`, which selects the suites and environments, with a runner.
162
-
The test runner builds the suites for the guest itself, and each entry uploads
163
-
JUnit reports and failure diagnostics as `e2e-results-<plan>-<runner>`. The job
164
-
is advisory and is not part of the `OpenShell / E2E` status yet.
159
+
The conformance lanes (`conformance-integration`) run the e2e suites through
160
+
`e2e-suites.yml` on the same prepared inputs. Each matrix entry pairs a plan
161
+
from `tests/plans/`, which selects the suites and environments, with a runner,
162
+
and optionally narrows it to one environment so environments run as parallel
163
+
jobs. The test runner builds the suites for the guest itself, and each entry
164
+
uploads JUnit reports and failure diagnostics as
165
+
`e2e-results-<plan>-<environment>`. Branch E2E, Release Dev, and Release
166
+
Qualification run the `cpu-tests` plan on the five amd64 environments: Ubuntu
167
+
with Docker (deb), K3s and HA K3s, and Fedora with rootful and rootless Podman
168
+
(rpm).
165
169
166
170
Three opt-in labels enable the long-running E2E suites:
167
171
@@ -561,7 +565,7 @@ The bot's full administrator documentation is internal to NVIDIA. The only comma
561
565
|---|---|
562
566
| `.github/workflows/branch-checks.yml` | Required non-E2E checks. Triggers on `push: pull-request/[0-9]+` for PR mirrors and `merge_group` for queued merges. |
563
567
| `.github/workflows/branch-e2e.yml` | Standard, GPU, Kubernetes HA, and Kubernetes credential-driver E2E. PR mirror pushes use `test:e2e`, `test:e2e-gpu`, and `test:e2e-kubernetes` labels; merge groups do not run E2E. |
564
-
| `.github/workflows/e2e-suites.yml` | Reusable matrix job that runs the e2e suites selected by plans in `tests/plans/` on the given runnersand uploads `e2e-results-<plan>-<runner>`. |
568
+
| `.github/workflows/e2e-suites.yml` | Reusable matrix job that runs the e2e suites selected by plans in `tests/plans/` on the given runners, optionally one environment per job, and uploads `e2e-results-<plan>-<environment or runner>`. Used by the conformance lanes. |
565
569
| `.github/workflows/build-binaries.yml`, `build-vm-driver.yml` | Shared binary matrices used by branch and release workflows. The VM driver remains separate because its build consumes the runtime binaries. |
566
570
| `.github/workflows/build-images.yml` | Builds and pushes multi-platform images, then uploads the same OCI images as workflow artifacts. |
567
571
| `.github/workflows/package-release-binaries.yml` | Packages raw build artifacts into release tarballs without rebuilding them. |
0 commit comments