Open odockal opened 4 months ago
I can run podman e2e with all those options here https://github.com/containers/podman-desktop-e2e/blob/3f67ea76241e040d261e5653046a033b3093423c/.github/workflows/podman-e2e-windows.yaml#L93 it is already supported
Do know you how to easily read them? I would love to have a really fast and easily readable workflow that is also stable.
As it is pretty hard to figure out particular failure or the test error cause on windows. One needs to check the workflow run, log, download artifacts and examine them. Then we see a problem on Podman Desktop side, which might be caused by previous tests (like the one using podman machine), or general problem with podman or podman machine.
given the problem like this one: https://github.com/containers/podman/issues/22439, where podman machine can be created and started without issues, so we do not observer the problem prior running the tests, it might get really hard to find a culprit.
This workflow should make sure to test basic podman machine functionality, like pulling an image, getting info from podman inside VM, etc.
Since the problem mentioned above was only visible when using rootful connection, the workflow will be testing rootful, rootless and with user-mode networking machines for basic functionality.
this way we can make sure to at least know, that something very basic is not broken.