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
Add link caching #8354
Add link caching #8354
Conversation
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
Baseline is 56 minutes. |
Hmm, this is failing with |
First changelog run took 43m. |
Docs build was 13 min without a cache, 11 min with cache. |
request the cache version of pytest-check-links clean up packages Revert "clean up packages" This reverts commit dc193e7. Fix ci script build api docs after link checks cache action must target directory break link check into two build and add hashing Ensure the cache dir exists Install docs requirements consolidate jobs again break changelog into its own job cleanup cache paths and increase test timeout fix timeout-minutes specifier try changing cache name and adding restore-keys try changing cache name and adding restore-keys Clean up cache handling Use matrix.group bump version requirement We weren't actually using a cache... Print the contents of the cache dir change the cache name consolidate to one build remove changelog build update restore-keys
Down to 10 min for the combined doc tests, impressive. Are we caching all link checks, or just the troublesome github ones? |
We cache all links for 24 hrs. |
Okay, that makes waaay more sense than what I was thinking (that we keep the cache forever). That's a really elegant solution to this very niche, very annoying issue |
References
Partially addresses #8117. Utilizes the new caching options in
pytest-check-links
(thanks @bollwyvl!).Docs builds go from >1hr total to a single ~10 minute build with a cache. I increased the time limit to 90 so as our change log grows we have some space when the cache is busted.
Code changes
Changes to CI script and GH Actions workflow
User-facing changes
CI builds will be much faster.
Backwards-incompatible changes
None