Paul Holzinger 5004e99e3b pkg/machine/hyperv: fix incorrect timeout ... The timeout is simply to low, I don't know the previous numbers were collected because they are simply wrong. A machine init takes around 50s total. And while the ready timeout itself could be shorter there is really no good reason to set such a low limit as it will cause wrong failures. This is currently flaking a lot in CI, I see it in most hyperV logs I looked at[1]. While there is likely another problem with the boot failures I think this added a ton of false positives as it errors out early. [1] https://github.com/podman-container-tools/podman/actions/runs/34146238887/job/101820830173 Fixes: dd28c14f8c ("hyperv: add timeout to vsock ready wait") Signed-off-by: Paul Holzinger <pholzing@redhat.com>		2026-09-08 12:42:15 +02:00
..
vsock	pkg/machine/hyperv: fix incorrect timeout	2026-09-08 12:42:15 +02:00
hutil.go	hyperv: propagate detailed error from Hyper-V permission checks	2026-05-25 00:10:18 +02:00
stubber.go	run go fix ./...	2026-09-04 11:53:04 +02:00
stubber_test.go	hyperv: propagate detailed error from Hyper-V permission checks	2026-05-25 00:10:18 +02:00
volumes.go	Add command podman system hyperv-prep	2026-04-29 23:00:29 +02:00