Spurious failure trying to checkout the repository

[emilyalbini]

We're experiencing spurious failures trying to checkout repositories on GitHub Actions:

Getting action download info
Download action repository 'actions/checkout@v1'
Warning: Failed to download action 'https://api.github.com/repos/actions/checkout/zipball/50fbc622fc4ef5163becd7fab6573eac35f8462e'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Warning: Back off 27.717 seconds before retry.
Warning: Failed to download action 'https://api.github.com/repos/actions/checkout/zipball/50fbc622fc4ef5163becd7fab6573eac35f8462e'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Warning: Back off 27.21 seconds before retry.
Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

• https://github.com/rust-lang-ci/rust/runs/1354000264
• https://github.com/rust-lang-ci/rust/runs/1352438239
• https://github.com/rust-lang-ci/rust/runs/1353148003
• https://github.com/rust-lang-ci/rust/runs/1354742853
• https://github.com/rust-lang-ci/rust/runs/1355418041

cc @rust-lang/infra

[emilyalbini]

Contacted GitHub Support on this, I see no way for us to mitigate the problem on our end.

[emilyalbini]

Another failure: https://github.com/rust-lang-ci/rust/runs/1354742853

[emilyalbini]

Another failure: https://github.com/rust-lang-ci/rust/runs/1354742853 (added it to the top comment too).

Enabled debug logging on rust-lang-ci/rust and opened #78754 as recommended by GitHub Support. Once another build fails we'll probably be able to drill down more into the cause. There is also another report of the same issue available at actions/checkout#376.

[ohsayan]

Following on from your comment in actions/checkout#376 (comment) the worst part about this is that it's impossible to repro this