ci: fix Windows curl llvm download failure#2089
Merged
lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom Mar 6, 2026
Merged
ci: fix Windows curl llvm download failure#2089lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom
lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom
Conversation
For a few days now, the Windows CI variants have been almost always failing due to unexplained inability to curl download the pre-built LLVM that we stashed on a Google drive, which has worked flawlessly for over a year. J.F. Panisset suggested: > Could be a wild goose chase, but a direction to look in with your > Windows / curl issue would be SSL certificate verification. Windows > uses some kind of magic process to update its store of recognized CA > root certs, but since a Windows runner is a "fresh" Windows VM every > time, it could be that it is missing an updated cert required to > verify the https URL you are downloading from (assuming that's using > a cert anchored to a root CA not in that base WIndows image). I've > seen issues like that on Windows systems with limited Internet > access. If you try curl --insecure to (temporarily) bypass > certificate verification, are you able to download what you need? And sure enough, adding --insecure clears it right up. Signed-off-by: Larry Gritz <lg@larrygritz.com>
Collaborator
Author
|
Merging to fix broken CI |
Contributor
|
Sorry didn't see this in time for an approval, but yes, that's a good workaround for now. |
lgritz
added a commit
to lgritz/OpenShadingLanguage
that referenced
this pull request
Mar 6, 2026
…#2089) For a few days now, the Windows CI variants have been almost always failing due to unexplained inability to curl download the pre-built LLVM that we stashed on a Google drive, which has worked flawlessly for over a year. J.F. Panisset suggested: > Could be a wild goose chase, but a direction to look in with your > Windows / curl issue would be SSL certificate verification. Windows > uses some kind of magic process to update its store of recognized CA > root certs, but since a Windows runner is a "fresh" Windows VM every > time, it could be that it is missing an updated cert required to > verify the https URL you are downloading from (assuming that's using > a cert anchored to a root CA not in that base WIndows image). I've > seen issues like that on Windows systems with limited Internet > access. If you try curl --insecure to (temporarily) bypass > certificate verification, are you able to download what you need? And sure enough, adding --insecure clears it right up. Signed-off-by: Larry Gritz <lg@larrygritz.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For a few days now, the Windows CI variants have been almost always failing due to unexplained inability to curl download the pre-built LLVM that we stashed on a Google drive, which has worked flawlessly for over a year.
J.F. Panisset suggested on Slack:
And sure enough, adding --insecure clears it right up.