I know this has been happening every so often. Let’s starting using the same topic from now on, to simplify who will get involved.
Before reporting a red build, do the following:
- Look the logs. Do they seem like a transient error like ‘timeout’ or similar? Do they complain about lack of disk space? Just try to run it again. They might go green and there’s nothing to report.
- Have you checked any comments on the build? Maybe someone already investigated it. Check the first red one.
- You still have no idea why it failed? Try to run the build again. Maybe some other snapshot got updated, and that will solve the problem. There’s no need to report a broken build if you haven’t tried to rerun it and it was red again. They are not broken, they might be flaky, but not broken.
- Did Reference Application build broke on Travis CI tests? You need to check the logs at travis CI to see what happened.
- Do you have a build that is particularly flaky? Please report. Not as broken, but as flaky. We can take a look on why that’s the case.
- Did a certain build became consistently red since a certain commit? You need to check the commit and see also which snapshots were modifying on that build.
Otherwise, please add it here. Let’s make a single topic, so we don’t get lost on too many mentions.
