summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2009-08-01 19:25:25 +0000
committerChris Lattner <sabre@nondot.org>2009-08-01 19:25:25 +0000
commit6778f1f3682c986cc830bfcb3173b22be660a5de (patch)
tree1d714b730bd0f6ad2f1349a2f23174131098d672 /llvm/docs
parentc278621694b19a5f721f24cf515aa785a97032fc (diff)
downloadbcm5719-llvm-6778f1f3682c986cc830bfcb3173b22be660a5de.tar.gz
bcm5719-llvm-6778f1f3682c986cc830bfcb3173b22be660a5de.zip
add a note about the build bots
llvm-svn: 77796
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/DeveloperPolicy.html9
1 files changed, 6 insertions, 3 deletions
diff --git a/llvm/docs/DeveloperPolicy.html b/llvm/docs/DeveloperPolicy.html
index 9c8b4d666b8..dd201848b2c 100644
--- a/llvm/docs/DeveloperPolicy.html
+++ b/llvm/docs/DeveloperPolicy.html
@@ -287,9 +287,12 @@ svn diff
</ul>
<p>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.</p>
+ 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.</p>
<p>Commits that violate these quality standards (e.g. are very broken) may be
reverted. This is necessary when the change blocks other developers from
OpenPOWER on IntegriCloud