Smallfu666 opened a new pull request, #12610:
URL: https://github.com/apache/gluten/pull/12610
## What changes are proposed in this pull request?
Part 2 of #12599, following up on #12602 (producer-side seeding, merged as
302e086d0).
Switches the ccache **restore** steps in the three consumer workflows listed
in the issue from `actions/cache` to the Apache Stash entries seeded by
`velox_backend_cache.yml`:
- `velox_backend_x86.yml` (3 sites: centos-7 static, centos-9 shared,
centos-9 cudf)
- `velox_backend_arm.yml` (2 sites: centos-8 static ARM64, centos-9 shared
ARM64)
- `velox_backend_enhanced.yml` (1 site: enhanced centos-7 static)
Design notes:
- Stash has no `restore-keys` prefix mechanism, so each restore uses the
exact key the producer saves under: `ccache-<variant>-${{
hashFiles('ep/build-velox/src/**') }}`. A PR that modifies the Velox build tree
therefore gets a cold ccache build, which is the safe behavior (the cache would
be stale for it anyway). The Stash restore action searches the PR's base
branch, so entries seeded from `apache/main` are visible to PR runs.
- Consumer-side `actions/cache` **save** steps are intentionally kept
unchanged, so reverting this PR instantly restores the previous behavior.
Removing the legacy `actions/cache` producer/consumer code is the final cleanup
stage of #12599 and will be submitted only after this restore path has been
validated in CI.
## How was this patch tested?
- Producer-side Stash entries were verified in the `apache/main` run of
`Velox backend Dependency Cache` after #12602 merged:
https://github.com/apache/gluten/actions/runs/30015073392 (all cache jobs saved
their Stash variant successfully, confirmed by @zhouyuan).
- All three modified workflow files pass YAML validation; the diff only
replaces the `Get Ccache` restore steps and leaves build/save/upload steps
untouched.
- The CI runs on this PR itself exercise the new Stash restore path end to
end.
## Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.8
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
