It seems that Angerman's Windows runners aren't fully configured as they don't have the Python requests library available, leading to failures in ghc/win32-tarballs>.
Edited
Designs
An error occurred while loading designs. Please try again.
Child items
0
Show closed items
GraphQL error: The resource that you are attempting to access does not exist or you don't have permission to perform this action
No child items are currently open.
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Ben Gamarichanged the descriptionCompare with previous version
@angerman, I think this is back in your court. It would be good if you could give @chreekat access to these machines so we don't have to bother you to address things like this.
A naive attempt to run Configure-GHC-Runner failed at this step:
Full system update with 'pacman --noconfirm -Su'...warning: database file for 'clangarm64' does not exist (use '-Sy' to download):: Starting core system upgrade...warning: terminate other MSYS2 programs before proceedingerror: failed to prepare transaction (could not find database)Command 'pacman --noconfirm -Su' did not complete successfully. ExitCode: 1At C:\Users\Administrator\windows-ci.ps1:35 char:5+ throw ("Command `'$command`' did not complete successfully. ExitC ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Command 'pacman...ly. ExitCode: 1:String) [], RuntimeException + FullyQualifiedErrorId : Command 'pacman --noconfirm -Su' did not complete successfully. ExitCode: 1
There are other idempotency issues, but I'm pretty sure requests did get reinstalled on win-1. I have unpaused the runner. I will continue again tomorrow with win-2 and continue to make improvements to idempotency.
Ben Gamarichanged the descriptionCompare with previous version
I have now rerun that failed job on both windows runners and the error did not resurface on either of them. The issue is either now fixed or it is intermittent.
I ran the setup script on win-1, but haven't touched win-2 yet.
I am still going to update win-2 right now, but I will close this issue and we can dig deeper if the problem happens again.