Skip to content
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

Nightly tests did not succeed on fedora-39/podman-next: TestApplication.testCheckpointRestore regression #1495

Closed
cockpituous opened this issue Dec 2, 2023 · 2 comments
Assignees
Labels

Comments

@cockpituous
Copy link
Contributor

Tests failed on 39de27b, logs

@martinpitt martinpitt changed the title Nightly tests did not succeed on fedora-39/podman-next Nightly tests did not succeed on fedora-39/podman-next: checkpoint restore regression Dec 3, 2023
@martinpitt martinpitt self-assigned this Dec 3, 2023
@martinpitt martinpitt changed the title Nightly tests did not succeed on fedora-39/podman-next: checkpoint restore regression Nightly tests did not succeed on fedora-39/podman-next: TestApplication.testCheckpointRestore regression Dec 4, 2023
@martinpitt
Copy link
Member

The error message in the screenshot points to restore.log which says

(00.000000) Unable to get $HOME directory, local configuration file will not be used.
(00.000044) Version: 3.18 (gitid 0)
(00.000052) Running on fedora-39-127-0-0-2-2201 Linux 6.6.2-201.fc39.x86_64 containers/podman#1 SMP PREEMPT_DYNAMIC Wed Nov 22 21:31:42 UTC 2023 x86_64
(00.000072) Loaded kdat cache from /run/criu/criu.kdat
(00.000131) Hugetlb size 2 Mb is supported but cannot get dev's number
(00.000141) Hugetlb size 1024 Mb is supported but cannot get dev's number
(00.000716) Error (criu/files.c:1590): Can't fstat inherit fd 6: Bad file descriptor

I get the same error with podman container restore swamped-crate after the test failed.

It also happens with a pure CLI test:

podman run -dit --name t1 --stop-timeout 0 localhost/test-busybox:latest sh
podman container checkpoint t1
podman container restore t1

It even fails with the most basic test:

podman run -d --name t1 localhost/test-busybox:latest sleep 1000
podman container checkpoint t1
podman container restore t1

@martinpitt
Copy link
Member

Reported to containers/crun#1367 . Let's give the podman devs today to sort it out. If it's still broken tomorrow, we'll get a new nightly failure and I'll naughty it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants