mirror of https://github.com/llvm/torch-mlir
031d127940
Until recently, we had to either risk feature branches creating PyTorch build caches (which were unusable by the main branch or other parallel feature branches because of GitHub's rules around sharing caches among branches) or we had to limit the PyTorch build caches to only the main branch, causing CI runs on feature branches to be terribly slow because they had to rebuild PyTorch each time. This patch enables the best of both worlds, by using a fork (github.com/ashay/cache) of the GitHub's cache action, where the fork adds an option (called `save`) which, when set, uploads a new cache entry. We thus set this `save` flag only when we're building PyTorch from source in Torch-MLIR's main branch, whereas all other builds set this `save` flag to `false`. The ability to conditionally update the cache has been an oft-requested feature on the original (github.com/actions/cache) repository and multiple unmerged PRs exist to allow conditional cache updates, so it is likely that using the fork is only a temporary solution. |
||
|---|---|---|
| .. | ||
| RollPyTorch.yml | ||
| bazelBuildAndTest.yml | ||
| buildAndTest.yml | ||
| buildRelease.yml | ||
| gh-pages-releases.yml | ||
| oneshotSnapshotPackage.yml | ||
| releaseSnapshotPackage.yml | ||