Skip to content

Spurious failure trying to checkout the repository #78743

Closed
Closed
Spurious failure trying to checkout the repository#78743
Labels
A-github-actionsArea: GitHub Actions (GHA)A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)C-bugCategory: This is a bug.P-highHigh priorityT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

Description

@emilyalbini
emilyalbini
opened on 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

Activity

  1. emilyalbini
    added
    P-highHigh priority
    A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)
    T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
    C-bugCategory: This is a bug.
    on Nov 4, 2020

  2. emilyalbini commented on Nov 4, 2020

    @emilyalbini
    emilyalbini
    on Nov 4, 2020
    MemberAuthor

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

  3. emilyalbini commented on Nov 4, 2020

    @emilyalbini
    emilyalbini
    on Nov 4, 2020
    MemberAuthor

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

  4. emilyalbini
    added a commit that references this issue on Nov 4, 2020

    ci: bump actions/checkout to version 2

    308dbdd

  5. emilyalbini commented on Nov 4, 2020

    @emilyalbini
    emilyalbini
    on Nov 4, 2020
    MemberAuthor

    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.

  6. JohnTitor
    added a commit that references this issue on Nov 5, 2020

    Rollup merge of rust-lang#78754 - pietroalbini:checkout-v2, r=Mark-Si…

    b0d2f97
  7. bors
    added a commit that references this issue on Nov 5, 2020

    Auto merge of rust-lang#78754 - pietroalbini:checkout-v2, r=Mark-Simu…

    8c20701
  8. camelid
    added
    A-github-actionsArea: GitHub Actions (GHA)
    on Nov 6, 2020

  9. ohsayan commented on Nov 6, 2020

    @ohsayan
    ohsayan
    on Nov 6, 2020
    Contributor

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

  10. emilyalbini commented on Nov 11, 2020

    @emilyalbini
    emilyalbini
    on Nov 11, 2020
    MemberAuthor

    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.

  11. emilyalbini commented on Nov 25, 2020

    @emilyalbini
    emilyalbini
    on Nov 25, 2020
    MemberAuthor

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

  12. emilyalbini
    closed this as completedon Nov 25, 2020

  13. ohsayan commented on Nov 25, 2020

    @ohsayan
    ohsayan
    on Nov 25, 2020
    Contributor

    @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

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-github-actionsArea: GitHub Actions (GHA)A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)C-bugCategory: This is a bug.P-highHigh priorityT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions