llvm dev - Oct 2015 - Revisions that cause buildbot problems but aren't on blame lists

I've investigated several failures that my buildbots detected but when I 
figured out which revisions caused the failures they weren't on any 
blame lists.  Thus the developer has no clue they broke anything until I 
contact them.

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.

Should the bots be including their test cases in determining blame lists 
and when to run or was this left off on purpose?
-- 

-Bill Seurer

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.
Hi Bill,

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
infrastructure).

Galina,

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?

cheers,
--renato

Hi,

I've had this problem on a compiler-rt change too. It was on the
clang-cmake-mips builder earlier this week.
________________________________________
From: llvm-dev [llvm-dev-bounces at lists.llvm.org] on behalf of Renato Golin
via llvm-dev [llvm-dev at lists.llvm.org]
Sent: 30 October 2015 08:34
To: Bill Seurer
Cc: LLVM Dev
Subject: Re: [llvm-dev] Revisions that cause buildbot problems but aren't on
blame lists

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.
Hi Bill,

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
infrastructure).

Galina,

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?

cheers,
--renato
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev