leanprover / leanprover/lean-action
Add tests for GitHub caching behavior
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 45
- Forks
- 22
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 1
Description
GitHub caching with actions/cache have been the cause of multiple issues (#96, #116). Currently the functional test suite disables actions/cache with use-github-cache: false, so caching behavior is not as well documented and not checked when changes are proposed.
We may have to add some testing outputs to properly test caching behavior.
Test ideas
- run
lean-actiontwice and verify the cache from the first job is restored on the second job - run
lean-actionin a matrix of jobs where none should share caches
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the functional test suite and its current use-github-cache: false setting. Run the existing lean-action tests, then add coverage for running lean-action twice and for a matrix where jobs should not share caches. Done means the first run's cache is restored on the second and matrix jobs remain isolated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100