-
Notifications
You must be signed in to change notification settings - Fork 119
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
Use caching to speed up functional tests #10053
Conversation
5d97a67
to
1bd9c6a
Compare
b98c804
to
282d0d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Looking at the env, maybe we should continue splitting up the files to avoid downloading things we dont need, there are a lot of dependencies we pull that are depending on the target you need :/
Maybe time to switch to micromamba? Resolving and fetching is pretty fast! And its only one static executable :) |
Description
The functional tests are slow, and it sucks. Here are some tweaks to make it go faster:
ccache
which we'll use to cache compiled objects.actions/cache@v4
to save the results of the ccache folder on everypush
actions/cache@v4
to pull the ccache folder from the PR's base commit.Some future work to make it go even faster:
ccache
and they are slow to build. However, they don't change very often so maybe we should just cache the generated libs?Reference
Checklist