kumarUjjawal opened a new pull request, #25231: URL: https://github.com/apache/datafusion/pull/25231
## Which issue does this PR close? Part of #25148. ## Rationale for this change Five feature-check jobs currently run without a Rust dependency cache. Reusing compatible compilation artifacts should reduce repeated dependency compilation and CI runner usage while preserving the existing feature checks and parallel jobs. ## What changes are included in this PR? - Add dependency caching to the `datafusion-common`, `datafusion-proto`, `datafusion-ffi`, `datafusion-functions`, and `datafusion-spark` feature-check jobs using the existing `amd-ci-check` key. - Let the functions check save the cache on `main` to populate GitHub's cache backend. The workspace check already saves to the separate Runs-On cache backend. The other four jobs only restore caches. - Clarify the cache comments. Job names, runner choices, feature-check commands, and required checks remain unchanged. ## What is the testing strategy for this PR? - Compared the parsed workflows before and after the change: removing the five new cache steps produces the original configuration, including all 26 jobs and their commands. - `python3 ci/scripts/check_asf_yaml_status_checks.py` passed for all 35 required checks. - `ci/scripts/check_no_cargo_install_in_workflows.sh`, targeted spelling checks, and `git diff --check` passed. - Actionlint passed for the complete cache producer and consumer job definitions. Full-workflow actionlint still reports existing `parallel` blocks and a numeric service-port lookup outside the changed jobs. This changes workflow configuration only. Cache hit rates and elapsed-time savings need measurement in hosted CI with populated caches. A cache miss still compiles dependencies and runs the existing checks. ## Are there any user-facing changes? No. -- 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]
