You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They are new and failing on remote, needs to be looked at (containers#25138)
For now skip them so we can have a proper buildah vendored for rc2.
Signed-off-by: Paul Holzinger <[email protected]>
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Jan 27, 2025
They are new and failing on remote, needs to be looked at (containers#25138)
For now skip them so we can have a proper buildah vendored for rc2.
Signed-off-by: Paul Holzinger <[email protected]>
I am not sure if these tests should be triggerd in remote or not, because the modification signature of file are changed everytime when files are sent from client to backend causing the cache burst, in case of remote setup and we cant do these calculations on client side since processing of Containerfile only happens on backend.
Well if caching does not work with remote here that limits a lot of users (given windows/macos...)
Isn't the proper solution to teach the remote client when sending the tarball to preserve the file modified time and other file attributes that are used to check for cache invalidation?
Seen in the latest buildah vendor (#25130) which added a new cache feature for mount content (containers/buildah#5691).
Two new test caes are failing with podman-remote:
Failing log: https://api.cirrus-ci.com/v1/artifact/task/5781189207785472/html/bud-remote-fedora-41-root-host-sqlite.log.html
I am going to skip them on remote for now but I think this should be investigated.
The text was updated successfully, but these errors were encountered: