forked from electronicarts/CnC_Generals_Zero_Hour
-
Notifications
You must be signed in to change notification settings - Fork 167
ci(vcpkg): Fix recurring binary cache invalidation from runner image updates #2371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
bobtista
wants to merge
3
commits into
TheSuperHackers:main
Choose a base branch
from
bobtista:bobtista/fix-vcpkg-ci-cache-stability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+18
−13
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| # Include the default x86-windows triplet | ||
| set(VCPKG_TARGET_ARCHITECTURE x86) | ||
| set(VCPKG_CRT_LINKAGE dynamic) | ||
| set(VCPKG_LIBRARY_LINKAGE dynamic) | ||
|
|
||
| # Exclude compiler version from ABI hash so that weekly GitHub runner image | ||
| # updates don't invalidate the binary cache. Minor MSVC version bumps do not | ||
| # cause ABI incompatibilities for this project. | ||
| set(VCPKG_DISABLE_COMPILER_TRACKING ON) | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this possibly cause other issues in the future? If the binary cache is invalidated once a week, then why does it not keep the new binary cache after 1 build? Does that not need looking into?
Do we perhaps need a CI trigger to manually force purge and refresh the cache in case it is accidentially broken?
Do we know why exactly the cache is broken right now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two separate layers of caching.
So the problem was GitHub Actions says: "key v2-msvc14.44-... matches, here's your directory" and says cach-hit was true. Then vcpkg opens that directory, computes its hash with the full compiler version 14.44.35207, finds no matching .zip files (they were built with 14.43.xxxxx) and re-builds ffmpeg which takes forever (17 min). Because cache-hit was true as far as github is concerned, it doesn't save the new build. This fix removes the compiler version from vcpkg's hash, so both layers should stay in sync.
RE future issues, MSVC maintains ABI compatibility within the same major version (14.x), and the cache still invalidates when the vcpkg baseline or triplet config changes. We'd be very unlikely to have no other changes before the next major MSVC version - and yes we can always just bump the version in build-toolchain.yml to force purge and refresh the cache.