Skip to content
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

Fix cache related build problem - error LNK4020 #1583

Merged
merged 5 commits into from
Feb 15, 2025
Merged

Conversation

DanRStevens
Copy link
Member

I believe this fixes #1553, though we may not know for a little while if the error comes up again or not.

Previously we used the key from the restore step as a way of ensuring the save key would match, even if the restore key was modified. Now we have an env var with the value, so we can use that to ensure consistency between restore and save.

In some cases we may skip the restore step, in which case the restore step won't have a cache key set. In those cases it's better to use the env var, which will always be set.
If the earlier restore step is skipped, then there are no output values set. In that case, the `cache-hit` output value would be blank. A blank value is not `true`. Hence the first check for `cache-hit` being not true is sufficient to cover this case too.
@DanRStevens DanRStevens merged commit 3d8bba3 into main Feb 15, 2025
7 checks passed
@DanRStevens DanRStevens deleted the fixCacheProblem branch February 15, 2025 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix build caching related error LNK4020
1 participant