[llvm-dev] Revisions that cause buildbot problems but aren't on blame lists
Renato Golin via llvm-dev
llvm-dev at lists.llvm.org
Fri Oct 30 08:34:44 PDT 2015
On 30 October 2015 at 14:48, Bill Seurer via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> It appears this happens when (for instance) one of the test cases in
> projects/test-suite is updated and causes a failure. Such a revision also
> won't kick off a new test cycle.
This is a known issue, and maybe we should look into that, now that
the two other critical issues (silent master and ignoring exceptions)
are done. Another repository that has the same effect is Zorg (the bot
First, the easy one: I think we should include Zorg on *all* monitors.
The not so easy one: I believe this is just a matter of creating a
monitor based on the test-suite, and put all test-suite bots checking
on it too. But from what I remember, you can only create lists of
monitors, not necessarily collate them per bot. Is that true?
More information about the llvm-dev