Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spurious failure trying to checkout the repository #78743

Closed
pietroalbini opened this issue Nov 4, 2020 · 7 comments
Closed

Spurious failure trying to checkout the repository #78743

pietroalbini opened this issue Nov 4, 2020 · 7 comments
Labels
A-github-actions Area: GitHub Actions (GHA) A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. P-high High priority T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@pietroalbini
Copy link
Member

pietroalbini commented Nov 4, 2020

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.

cc @rust-lang/infra

@pietroalbini pietroalbini added P-high High priority A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. C-bug Category: This is a bug. labels Nov 4, 2020
@pietroalbini
Copy link
Member Author

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

@pietroalbini
Copy link
Member Author

pietroalbini added a commit to pietroalbini/rust that referenced this issue Nov 4, 2020
This was recommended by GitHub Support to try reducing the things that
could've caused rust-lang#78743. I checked the changelog and there should be no
practical impact for us (we already set an explicit fetch-depth).
@pietroalbini
Copy link
Member Author

pietroalbini commented Nov 4, 2020

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.

JohnTitor added a commit to JohnTitor/rust that referenced this issue Nov 5, 2020
…mulacrum

Bump actions/checkout to version 2

This was recommended by GitHub Support to try reducing the things that could've caused rust-lang#78743. I checked the changelog and there should be no practical impact for us (we already set an explicit fetch-depth).

r? `@Mark-Simulacrum`
bors added a commit to rust-lang-ci/rust that referenced this issue Nov 5, 2020
…lacrum

Bump actions/checkout to version 2

This was recommended by GitHub Support to try reducing the things that could've caused rust-lang#78743. I checked the changelog and there should be no practical impact for us (we already set an explicit fetch-depth).

r? `@Mark-Simulacrum`
@camelid camelid added the A-github-actions Area: GitHub Actions (GHA) label Nov 6, 2020
@ohsayan
Copy link
Contributor

ohsayan commented Nov 6, 2020

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

@pietroalbini
Copy link
Member Author

Since we didn't see any new error since the last comment, and because debug logging is noisy, I'm disabling debug logging. If the error happens again, someone on the infra team will need to set the ACTIONS_RUNNER_DEBUG and ACTIONS_STEP_DEBUG secrets to true in the rust-lang-ci/rust repository.

@pietroalbini
Copy link
Member Author

We haven't seen this in a while, closing the issue.

@ohsayan
Copy link
Contributor

ohsayan commented Nov 25, 2020

@pietroalbini Pretty much the same; we haven't seen this happen lately either

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-github-actions Area: GitHub Actions (GHA) A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. P-high High priority T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants