-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[It] podman machine cp
fails when run on windows-2025 GH runner for 5.5.0-rc2
#26056
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Created as a placeholder. This needs to be tested with Windows Server 2025 host to see if this is reproducible outside of the runner image. |
I have reproduced this same error while testing if e2e tests work on arm64 Windows (I have reproduced it on a Windows 11 Pro version 10.0.26100 build 26100). I am preparing a PR to fix it. |
l0rd
added a commit
to l0rd/podman
that referenced
this issue
May 21, 2025
The podman machine copy test "attempt copying file to a new directory" was failing because on recent version of Windows the error message doesn't match the expected error message. To make it work on new and old version of Windows both old and new error messages are now considered as valid. Fixes containers#26056 Signed-off-by: Mario Loriedo <[email protected]>
l0rd
added a commit
to l0rd/podman
that referenced
this issue
May 21, 2025
The podman machine copy test "attempt copying file to a new directory" was failing because on recent version of Windows the error message doesn't match the expected error message. To make it work on new and old version of Windows both old and new error messages are now considered as valid. Fixes containers#26056 Signed-off-by: Mario Loriedo <[email protected]>
l0rd
added a commit
to l0rd/podman
that referenced
this issue
May 21, 2025
The podman machine copy test "attempt copying file to a new directory" was failing because on recent version of Windows the error message doesn't match the expected error message. To make it work on new and old version of Windows both old and new error messages are now considered as valid. Fixes containers#26056 Signed-off-by: Mario Loriedo <[email protected]>
l0rd
added a commit
to l0rd/podman
that referenced
this issue
May 21, 2025
The podman machine copy test "attempt copying file to a new directory" was failing because on recent version of Windows the error message doesn't match the expected error message. To make it work on new and old version of Windows both old and new error messages are now considered as valid. Fixes containers#26056 Signed-off-by: Mario Loriedo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Issue Description
This test started to fail with error message assertions, when run on windows-2025 runner (details in result logs).
Steps to reproduce the issue
Steps to reproduce the issue
./winmake localmachine "cp_test.go"
Describe the results you received
Assertion failed
Example run with windows-2025 https://github.com/arixmkii/qcw/actions/runs/14800785991/job/41558841884
Describe the results you expected
No error
Example run with windows-2022 runner https://github.com/arixmkii/qcw/actions/runs/14800643299/job/41558373745
podman info output
5.5.0-rc2 built from tag
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Standard github runner environment, runner windows-2025
Additional information
Issue is specific for windows-2025 runner, probably something specific to Windows 2025 server or some specifics of the
scp
bundled with that runner.The text was updated successfully, but these errors were encountered: