TRAP Caching: Re-introduce workaround for download timeout #1373
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.
Looking at our telemetry, I found a run where the download timeout provided by the Actions library didn't do what we expect. In particular, looking at the timestamps shows that while the downloading happened quickly, the check to see if the key was present in the cache took over 15 minutes (much longer than our 2 minute timeout). Clearly, this is problematic. While it isn't a widespread problem as far as I can see in our telemetry, an outage in the Actions cache could cause this to break all CodeQL runs which is not good.
Let's use our workaround that wraps the entire call in a timeout here too like we already do for uploading.
Merge / deployment checklist