You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't done extensive testing to verify this is the case, but it seems to me that the cache key doesn't take the value of vcpkgTriplet into account. Given the following:
If I have x86-windows and x64-windows in my matrix, it seems like they both try to save under the same cache key. This means that every time the workflow is triggered, one of them gets rebuilt, since they are stepping on each other. I added appendedCacheKey: "42-pazer-${{ matrix.triplet }}" and it seemed to resolve the issue.
The text was updated successfully, but these errors were encountered:
@PazerOP yes, I think adding vcpkgTriplet input content to the cache's key is helpful.
Also, as suggested here I would recommend the usage of the response file, which contains both packages and triplet, and 'vcpkg as a submodule', so you do not have to specify anything in the workflow other than the reponse file.
I haven't done extensive testing to verify this is the case, but it seems to me that the cache key doesn't take the value of
vcpkgTriplet
into account. Given the following:If I have
x86-windows
andx64-windows
in my matrix, it seems like they both try to save under the same cache key. This means that every time the workflow is triggered, one of them gets rebuilt, since they are stepping on each other. I addedappendedCacheKey: "42-pazer-${{ matrix.triplet }}"
and it seemed to resolve the issue.The text was updated successfully, but these errors were encountered: