[llvm-dev] Revisions that cause buildbot problems but aren't on blame lists

[Bill Seurer via llvm-dev]

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