Skip to content

macOS builders randomly stops working on GitHub Actions #71988

Closed

Activity

  1. added
    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.
    on May 7, 2020
  2. emilyalbini commented on May 8, 2020

    @emilyalbini
    MemberAuthor
  3. emilyalbini commented on May 11, 2020

    @emilyalbini
    MemberAuthor
  4. RalfJung commented on May 14, 2020

    @RalfJung
    Member

    This broke the 2nd rollup in a row: #72187
    Makes it kind of hard to land anything, really.^^

    There's no error, just a red cross next to "upload artifacts to S3".

  5. emilyalbini commented on May 14, 2020

    @emilyalbini
    MemberAuthor

    We have a call with Github today, if there is no news we'll rollback the gate on GHA.

  6. emilyalbini commented on May 14, 2020

    @emilyalbini
    MemberAuthor

    GitHub is going to continue looking into this ❤️

    In the meantime I'll remove the double-gate, to let the queue run more smoothly.

  7. emilyalbini commented on May 14, 2020

    @emilyalbini
    MemberAuthor

    Removed the gate on GHA.

  8. RalfJung commented on May 14, 2020

    @RalfJung
    Member

    @pietroalbini thanks!
    Does this take effect on the already running #72202 (comment) ?

  9. emilyalbini commented on May 14, 2020

    @emilyalbini
    MemberAuthor

    It should.

  10. Aaron1011 commented on May 18, 2020

    @Aaron1011
    Contributor
  11. emilyalbini commented on Jul 3, 2020

    @emilyalbini
    MemberAuthor

    Just got another failure related to this:

  12. added a commit that references this issue on Jul 23, 2020
  13. youknowone commented on Jul 24, 2020

    @youknowone
    Contributor

    I am getting similar experience in other rust project, so happy to see Github is looking into this issue.

  14. thejoebourneidentity commented on Jul 29, 2020

    @thejoebourneidentity

    Thanks to everyone for their patience on this issue, I work on the GitHub Actions compute platform that powers our runners and wanted to share an update.

    We're aware of the issue and have multiple members of our team across our entire hardware stack actively working on it. We've been able to identify a specific data center that may be the primary failure point. We're rapidly building out additional telemetry and alerting to help us find the root cause. Stay tuned, we want to fix this as soon as possible.

  15. matthewmccullough commented on Jul 29, 2020

    @matthewmccullough

    We're aware of the issue have multiple members of our team across our entire hardware stack actively working on it. We've been able to identify a specific data center that may be the primary failure point. We're rapidly building out additional telemetry and alerting to help us find the root cause. Stay tuned, we want to fix this as soon as possible.

    @thejoebourneidentity Thanks for the insight into the bug investigation and reiteration that you and the team are working on it.

  16. alepauly commented on Aug 27, 2020

    @alepauly

    @pietroalbini We continue looking at this and I wanted to confirm you are still seeing the exact same symptoms of disconnects. We've been able to curve the cases where the runner disconnects and are now focusing more on perf issues that might be leading to timeouts. I browsed a few workflows and noticed timeouts such as this. Is this a good illustration of the current problem or are you seeing disconnects at a high rate still? Thanks!

  17. emilyalbini commented on Aug 27, 2020

    @emilyalbini
    MemberAuthor

    @alepauly thanks for getting back to us! Indeed, it seems like the runner disconnects are not appearing anymore! I'll monitor closely the build results in the coming week to see if they appear.

    Regarding the cancelled builds, like the one you mentioned, that's a mistake on our end 😅. Since our build matrix is so big we built an action to cancel builds once a new commit is pushed to the branch. While this is not a problem normally since our queue bot only pushes a new commit to the test branch when the previous one finishes, we're not gating our builds on the macOS builders yet due to this issue, so the queue bot isn't waiting for them to finish before pushing the new commit (causing the action to cancel the build).

    I opened a PR to disable the build cancellation for the macOS jobs, so the cancellations should disappear as soon as the PR lands. If we don't see any other spurious failure for a while we'll try to gate our builds on macOS again!

    Thanks again for looking into this issue ❤️

  18. added a commit that references this issue on Aug 27, 2020
  19. emilyalbini commented on Sep 3, 2020

    @emilyalbini
    MemberAuthor

    It seems a runner disappeared only one time across the whole week, which is definitely an improvement!

    I'll propose during the next weekly infrastructure team meeting to try and double-gate macOS on both Azure and GitHub Actions, to see what the impact would be on our queue size.

  20. alepauly commented on Sep 3, 2020

    @alepauly

    It seems a runner disappeared only one time across the whole week, which is definitely an improvement!

    We'll look at it on our end, we expect this to be better but not fully solved yet. Thanks for the report.

  21. added a commit that references this issue on Sep 15, 2020
  22. emilyalbini commented on Nov 16, 2020

    @emilyalbini
    MemberAuthor

    We didn't see it anymore for months, closing this. Thanks to everyone involved in fixing this! ❤️

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)O-macosOperating system: macOST-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