I'm frequently getting random mails informing me about a failed CI Job, but I'm unable to correlate this to any activity in a PR.

Mails have a subject like

[stephan-herrmann/eclipse.jdt.core] Run failed: Continuous Integration - issue3328 (d773ff0)

In many cases the CI Job claims failure right when the PR build succeeds.

In the mail body it says

Continuous Integration: Some jobs were not successful

And when I click on the button "View workflow run" I'm taken to a page, where the best way to inspect the cause of failure is to download many megabytes of raw build logs. No summary of the failure of any kind.

@mickaelistria Is this the feature introduced by #1254 ?

Does anyone wait for a CI Job on the fork to succeed before submitting a PR? Why? Do people even know where to look for build success in this scenario?

If there's no significant demand for this, my vote is for removing it.

Otherwise someone should

• ensure that it produces the same results as the PR build
• help people to get meaningful information from the result page.