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

[emilyalbini]

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:

• https://github.com/rust-lang/rust/runs/191033192
• https://github.com/rust-lang/rust/runs/191276265

Any idea why this is happening @rylev @ethomson?

cc @RalfJung

[Mark-Simulacrum]

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

[emilyalbini]

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

[lkillgore]

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]

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]

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]

Closing this since Azure Pipelines is no longer being used.