a 'make check' workflow

[Daniel Shahaf <da...@apache.org>]

My favourite use of the VM we have at ASF:

[[[
# curl -o foo.diff http://article.gmane.org/gmane.comp.version-control.subversion.devel/126999/raw
% cat foo.diff | ssh svn-qavm.a.o ./check $nickname
% sleep 720
% head -1 INBOX
Date: Mon, 04 Apr 2011 09:45:56 +0000
From: danielsh@svn-qavm.apache.org
To: danielsh@svn-qavm.apache.org
Subject: ./check@svn-qavm: $nickname: done: 20110404-09:33:52
Message-Id: <20...@svn-qavm.apache.org>

make: *** [check] Error 1
URL: https://svn.apache.org/repos/asf/subversion/trunk
Revision: 1088524



patching file subversion/libsvn_client/merge.c
Hunk #3 succeeded at 8702 (offset 21 lines).


Running tests in svnadmin_tests.py [73/88]....................FAILURE
Running tests in tree_conflict_tests.py [81/88]...............FAILURE
At least one test XPASSED, checking /home/danielsh/src/svn/patches/tests.log
XPASS: tree_conflict_tests.py 22: tree conflict at directory external
At least one test FAILED, checking /home/danielsh/src/svn/patches/tests.log
FAIL:  svnadmin_tests.py 17: fsfs recovery checks missing revs / revprops files
Summary of test results:
  1439 tests PASSED
  41 tests SKIPPED
  49 tests XFAILED (2 WORK-IN-PROGRESS)
  1 test XPASSED
  1 test FAILED
]]]

Does a complete checkout/autogen/configure/make/'make check', saves the
full patch (including log message that patch(1) ignored) and tests
output aside, and mails me the highlights of the results (including
compiler warnings if any).  And faster than my local machine, too :)