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

Cache LazyFS binary in CI #16326

Open
Tracked by #15951
serathius opened this issue Jul 28, 2023 · 1 comment
Open
Tracked by #15951

Cache LazyFS binary in CI #16326

serathius opened this issue Jul 28, 2023 · 1 comment

Comments

@serathius
Copy link
Member

serathius commented Jul 28, 2023

What would you like to be added?

Cache LazyFS binary in CI

Why is this needed?

Reduce runtime by ~ minute (needs to confirmed)

@jmhbnz
Copy link
Member

jmhbnz commented Aug 8, 2023

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

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

No branches or pull requests

2 participants