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
My view is this is a natural evolution of #15956. We definitely don't want a dependency install and lazyfs compile happening every ci run.
Once the robustness job is running in a container, all we would need to do is setup a pipeline that builds a slightly customised version of the golang:1.19-bullseye image that we currently use which has lazyfs dependencies and make install-lazyfs already run as an additional layer.
Edit: One major challenge with adopting containers for the robustness tests is that it is difficult to do anything with fuse filesystems inside containers without making security compromises, refer: docker/for-linux#321
Edit: Got lazyfs working in arm64 container workflows, pr #16392
What would you like to be added?
Cache LazyFS binary in CI
Why is this needed?
Reduce runtime by ~ minute (needs to confirmed)
The text was updated successfully, but these errors were encountered: