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

Azure Pipelines sometimes doesn't report back its status to GitHub #63513

Closed
pietroalbini opened this issue Aug 13, 2019 · 6 comments
Closed
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@pietroalbini
Copy link
Member

It happened a few times that Azure Pipelines doesn't report back the build status to GitHub, causing the commits to be in a permament "in progress" state. For example, a few times it happened yesterday:

Any idea why this is happening @rylev @ethomson?

cc @RalfJung

@pietroalbini pietroalbini added T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. C-bug Category: This is a bug. labels Aug 13, 2019
@Mark-Simulacrum
Copy link
Member

FWIW, I've also seen the checks just not starting, possibly after force pushing.

@pietroalbini pietroalbini added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Aug 13, 2019
@pietroalbini
Copy link
Member Author

Happened again for a bors merge on rustc: https://github.com/rust-lang/rust/runs/192177675

@lkillgore
Copy link

Hi @pietroalbini, I see from our telemetry the check-runs issue. I'm tracking down the problem with GitHub now. I'll reply back on this ticket when I have something more to report. Apologies for the inconvenience.

@lkillgore
Copy link

Quick update: I've made a few changes that seem to have mitigated the problem for now (I'm not seeing the error in our telemetry for your account). I'm still working at verifying the root cause.

@lkillgore
Copy link

Quick update: I think we found the root cause, and we have a fix, which should roll out over the next few days. It appears the last mitigation I mentioned didn't fix the problem completely; our telemetry reports that your account had additional failures afterward. I made another change, and I haven't noticed this problem on your account for the last few hours, so I think you should be good-to-go. Please post back here if you notice any check-runs failures over the next few days. I apologize for the inconvenience this caused.

@rylev
Copy link
Member

rylev commented Jan 14, 2021

Closing this since Azure Pipelines is no longer being used.

@rylev rylev closed this as completed Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. 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

4 participants