On 01/12/2024 17:05, Brian Inglis via Cygwin-apps wrote:
Hi folks,
Some Scallywag job steps are failing in cygwin-install-action with
message "Unable to connect to the remote server".
So far only arch and noarch - both package arch and null noarch - build
steps have been affected - not source builds.
Summary below - full log attached - also see my recent wget2 builds
"pending"/"failed" with this reason:
[...]
2024-12-01T12:20:55.2472465Z Invoke-WebRequest : Unable to connect to the
remote server
2024-12-01T12:20:55.2473117Z At
D:\a\_temp\ffa78816-f5f6-4b47-a993-27b435120c18.ps1:10 char:1
2024-12-01T12:20:55.2474131Z + Invoke-WebRequest
https://cygwin.com/setup-$platform.exe -OutFile C:\ ...
2024-12-01T12:20:55.2474732Z +
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2024-12-01T12:20:55.2475223Z + CategoryInfo : InvalidOperation:
(System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
2024-12-01T12:20:55.2475654Z eption
2024-12-01T12:20:55.2476362Z + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
Thanks for reporting this.
I'm afraid the http service on sourceware.org/cygwin.com had a little
hiccup and was unavailable for a short while on Sunday.
Things should be back to normal now.
I'd like to make (i) cygwin-install-action more robust against such
transient problems (See [1]), and (ii) improve scallywag so it retries
jobs which have failed to start properly like this, but SHTDI.
[1]
https://github.com/cygwin/cygwin-install-action/issues/9#issuecomment-2048182268
