adoroszlai opened a new pull request, #11665: URL: https://github.com/apache/ozone/pull/11665
## What changes were proposed in this pull request? `populate-cache` uses different key for [restoring](https://github.com/apache/ozone/actions/runs/39539462516/job/119023625580#step:3:16) and [saving](https://github.com/apache/ozone/actions/runs/39539462516/job/119023625580#step:11:17) the repo: ``` Run actions/cache/restore@v6 Cache not found for input keys: maven-repo-d88b382dcd41dffd4ea83f5ffd4d4974209efdd70b49180545b4151bf1ea27f1 ``` ``` Run actions/cache/save@v6 Failed to save: Unable to reserve cache with key maven-repo-0bf0547638bdaa049b27905cf2ab3d95fb4cb1c91d8d3d3ad87d45b6d8a807ad, another job may be creating this cache. ``` This is caused by extra `pom.xml` files that appear in `hadoop-ozone/ozonefs-hadoop[23]/target` (from shading). ``` hadoop-ozone/ozonefs-hadoop2/target/classes/META-INF/maven/com.fasterxml.jackson.core/jackson-annotations/pom.xml hadoop-ozone/ozonefs-hadoop2/target/classes/META-INF/maven/com.fasterxml.jackson.core/jackson-core/pom.xml ... ``` The result is that `scheduled-populate-cache` always builds the cache from scratch (daily). https://issues.apache.org/jira/browse/HDDS-17242 ## How was this patch tested? populate-cache: https://github.com/adoroszlai/ozone/actions/runs/39607793971/job/119248418934 ``` Cache not found for input keys: maven-repo-d88b382dcd41dffd4ea83f5ffd4d4974209efdd70b49180545b4151bf1ea27f1 ``` ``` Cache saved with key: maven-repo-d88b382dcd41dffd4ea83f5ffd4d4974209efdd70b49180545b4151bf1ea27f1 ``` -- 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]
