Since a while V > 5.1 we have flaky results in our CI because of caching.
It looks as if the tools are not properly installed form the cache:
Invoke-TrustedSigning: D:\a\_temp\db62da58-f888-4e54-ad0a-0984dad11162.ps1:212
Line |
212 | Invoke-TrustedSigning @params
| ~~~~~~~~~~~~~~~~~~~~~
| The term 'Invoke-TrustedSigning' is not recognized as a name of a cmdlet, function, script file, or executable
| program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
| again.
Error: Process completed with exit code 1.
Here is a failing run
https://github.com/mixxxdj/vcpkg/actions/runs/18787693773/job/53619922466
The cache size of 23 kB seems to be too small.
Cache hit for: TrustedSigning-0.5.3
Received 23579 of 23579 (100.0%), 0.1 MBs/sec
Cache Size: ~0 MB (23579 B)
Repeating the same run does not fix the issue.
Deleting TrustedSigning-0.5.3 form the cache normally fixes the issue.
But since the results are flaky we have no prove that this fixes actually the issue.
We have tried to install TrustedSigning ourself: mixxxdj/vcpkg#181 but it does not make a diffrence.
Since a while V > 5.1 we have flaky results in our CI because of caching.
It looks as if the tools are not properly installed form the cache:
Here is a failing run
https://github.com/mixxxdj/vcpkg/actions/runs/18787693773/job/53619922466
The cache size of 23 kB seems to be too small.
Repeating the same run does not fix the issue.
Deleting TrustedSigning-0.5.3 form the cache normally fixes the issue.
But since the results are flaky we have no prove that this fixes actually the issue.
We have tried to install TrustedSigning ourself: mixxxdj/vcpkg#181 but it does not make a diffrence.