[TEST] [OSS-ONLY] Implementing hashcode and mode based caching in 4X #3422
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.
Description
This commit implements a more efficient method of caching compilations. Cache now restored will now be guaranteed to compatible with the version and build configuration of compilations.
We will now save 5-8 mins in version upgrade and dump restore tests.
Key changes:
Implemented new format for cache keys which includes github hashcode of corresponding engine branch and build mode to better identify the cache stored in a key.
New format "ccache-engineHashcode-buildMode-extensionHashcode".
Cache restoration handled by build-modified-postgres.yml and saving by save-ccache.yml composite actions.
Removed timeStamp based caching.
Task: BABEL-5564
Signed-off-by: Siddharth Sengar [email protected]
Check List
By submitting this pull request,
I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.