-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Random build failures: Catalog the failures #1474
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
Comments
I wholeheartedly |
|
I've look in past two days (it's hard to look further, pages start load really slow) |
Point of this exercise is to look what is main pain point and allocate resources accordingly.
proposals for investigation:
|
Companion issue to #1471. We should investigate more fully at a high level why the builds are failing.
@eerhardt has helpfully provided a good list of these failures for builds that should have in principle succeeded, since they were against
master
. The task would then to be, somehow, to go through them, and determine why each has failed. This even has an analytics tab that will show the precise test failures, so perhaps this is not so hard of an issue! But getting a sense for why each has failed might itself be worthwhile, I imagine.While tests are I believe the primary culprit, I don't quite have an appreciation for how big of a problem it might be compared to other issues. For those builds that do not appear to be due to a test failure, why did they fail? Timeout? Network resources unavailable? Some other failure to setup? An actual failure to build somehow? (Of course some of these things, especially timeouts, could themselves be test failures.)
Also for those things that are test failures, which tests are failing, on what environments? I have a sense for some "usual suspects" of tests that are problematic, but I am sometimes surprised by new ones, and it would surely help to build a more complete catalog so that the investigation can focus its efforts usefully.
The text was updated successfully, but these errors were encountered: