I have an open JS project that utilizes public Github Actions. For the past 24 hours one of the builds started to fail with the same error, as it cannot fetch Yarn packages (i.e. yarn install
command):
Run yarn install
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
warning mini-css-extract-plugin@0.5.0: Invalid bin field for "mini-css-extract-plugin".
warning url-loader@1.1.2: Invalid bin field for "url-loader".
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://registry.yarnpkg.com/@material-ui/icons/-/icons-4.9.1.tgz: ESOCKETTIMEDOUT".
The error happens only to one of the builds, i.e. I have unit tests and binary build actions, which has exactly same install command, but only one of them always fails. Another one always works. Also it always works on other platforms, like ubuntu and macos. It had been working fine before yesterday, and there were no changes to build workflow in past week or so.
So it all looks like the build stuck with a Windows host that has a misconfigured networking. Is there any, probably hackish, way to force the build to run on another instance?