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.

Sign up for GitHub

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

Jump to bottom

[remote] checkpoint --file-lock test: new flake #12366

Closed
edsantiago opened this issue Nov 19, 2021 · 0 comments · Fixed by #12367
Closed

[remote] checkpoint --file-lock test: new flake #12366

edsantiago opened this issue Nov 19, 2021 · 0 comments · Fixed by #12367
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

The new checkpoint file-locks test (#12333) is failing in f34 remote

Expected
      <string>: Error: `/usr/bin/runc checkpoint --image-path /tmp/podman_test277192380/crio/vfs-containers/2ac9c9a5eb4262953b98f9bf3efaa2f6e8b5c2e22dea77d37b9caf7f7386cc2f/userdata/checkpoint --work-path /tmp/podman_test277192380/crio/vfs-containers/2ac9c9a5eb4262953b98f9bf3efaa2f6e8b5c2e22dea77d37b9caf7f7386cc2f/userdata 2ac9c9a5eb4262953b98f9bf3efaa2f6e8b5c2e22dea77d37b9caf7f7386cc2f` failed: exit status 1
  to contain substring
      <string>: criu failed

Weird thing is, criu failed does appear in the error message a few lines above. I have no time to diagnose this further today.

@rst0git PTAL
rst0git added a commit to rst0git/podman that referenced this issue Nov 19, 2021
@rst0git
test: Update error string for --file-locks test
84021cf 
Use a substring matching the end of the error message.

Closes: containers#12366

Signed-off-by: Radostin Stoyanov <[email protected]>
@rst0git rst0git mentioned this issue Nov 19, 2021
Merged
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test: Update error string for --file-locks test rst0git/podman
1 participant
@edsantiago