CI: Introduce per-PR kernel cache#9234
Merged
Merged
Conversation
chainer-ci
pushed a commit
to chainer-ci/cupy
that referenced
this pull request
Jul 12, 2025
CI: Introduce per-PR kernel cache
gpinkert
pushed a commit
to ROCm/cupy
that referenced
this pull request
Sep 13, 2025
CI: Introduce per-PR kernel cache
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces kernel caching for PRs.
Previously CI cache has only one layer. Cache is used for every PR but only updated after PR got merged. This made it difficult for PRs to complete CI within timeout if the PR's change contains cache-breaking changes, e.g. when modifying
cupy/_core/_include.This PR try to solve this problem by adding a second layer of cache - per-PR kernel cache. When testing PRs, both "main" cache (which is only updated after PR got merged) and "per-PR" cache are downloaded. After running CI in PRs, cache will be uploaded to "per-PR" cache.