divviup / divviup/divviup-android
Rust caching is less effective
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 1
- Avg merge
- 4h 13m
- Merged PRs (30d)
- 14
Description
Previously, the rust-cache action was working well for some of the Android targets, but lately they're all being rebuilt. The host target clippy run appears to be the only thing benefiting from caching. It's unclear how well the action supports cross-compilation targets. Perhaps we need to specify each nested target directly separately?
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 reviewing the GitHub Actions configuration for the rust-cache action and the Android cross-compilation targets. Compare the host clippy cache behavior with the Android target builds, then determine whether nested targets need separate cache configuration. Done means Android targets reuse their caches reliably instead of rebuilding on each run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions, rust
- Domain
- build-system, ci-cd, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100