test(e2e): run podman suite with tmachine - #3637
Conversation
|
Label |
75a79a6 to
917301f
Compare
917301f to
a919b73
Compare
a919b73 to
c42ffca
Compare
SDAChess
left a comment
There was a problem hiding this comment.
This looks good. Maybe as a follow-up we can consider cleaning up the testsuite running with a nextest role + renaming e2e to something more meaningful like podman-driver or something.
Yes. The |
c42ffca to
860421d
Compare
860421d to
894dd6e
Compare
Signed-off-by: Evan Lezar <elezar@nvidia.com>
Signed-off-by: Evan Lezar <elezar@nvidia.com>
Signed-off-by: Evan Lezar <elezar@nvidia.com>
894dd6e to
bf94eae
Compare
Summary
Migrate the portable Rust Podman E2E coverage from the legacy wrapper approach in #2982 to a dedicated tmachine test archive. Keep this coverage separate from the focused
driver-podmanuser-namespace suite and schedule both under driver-specific integration tests.Stack
Draft follow-up #3766 branches from #3597 for relay reconnect coverage.
Related Issue
No issue required: this is a focused test-infrastructure migration that supersedes draft PR #2982.
Merge after #3597, which replaces the removed
e2e/rust/tests/sync.rscoverage with portable file-transfer conformance scenarios.Changes
e2e-podmannextest archive frome2e/rustwith thee2e-podmanfeaturee2e-podmantestsuite and rootless Podman playbookdriver-podmansuite focused on default,auto,keep-id, and private UID-map equivalencepodman_usernsE2E binary now covered bydriver-podmansync.rsafter its file-transfer cases move to conformance in test(conformance): migrate file transfer coverage #3597Testing
mise run pre-commitpassesnix run .#build-artifacts-test-archivesnix run .#tmachine -- test fedora-podman-rootless binaries e2e-podman(43 passed, 2 skipped)nix run .#tmachine -- test fedora-podman-rootless binaries driver-podman(default,auto,keep-id, and private profiles passed)Checklist