From d7f10d33610fbf226e6e9425c534d0914fd012d4 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Sat, 1 Aug 2009 19:25:25 +0000 Subject: add a note about the build bots git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@77796 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/DeveloperPolicy.html | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 9c8b4d6..dd20184 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -287,9 +287,12 @@ svn diff

We prefer for this to be handled before submission but understand that it - isn't possible to test all of this for every submission. Our nightly testing - infrastructure normally finds these problems. A good rule of thumb is to - check the nightly testers for regressions the day after your change.

+ isn't possible to test all of this for every submission. Our build bots and + nightly testing infrastructure normally finds these problems. A good rule of + thumb is to check the nightly testers for regressions the day after your + change. Build bots will directly email you if a group of commits that + included yours caused a failure. You are expected to check the build bot + messages to see if they are your fault and, if so, fix the breakage.

Commits that violate these quality standards (e.g. are very broken) may be reverted. This is necessary when the change blocks other developers from -- cgit v1.1