Ulrich Windl wrote:
Quanah Gibson-Mount <quanah@zimbra.com> schrieb am 23.10.2013 um 19:12 inNachricht <921249C16E0FB2B352961386@[192.168.1.93]>:--On Wednesday, October 23, 2013 6:40 PM +0200 Patrick Lists <openldap-list@puzzled.xs4all.nl> wrote:Hi Quanah, On 10/22/2013 10:27 PM, Quanah Gibson-Mount wrote:If you know how to build OpenLDAP manually, and would like to participate in testing the next set of code for the 2.4.37 release, please do so. Generally, get the code for RE24: <http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=snapshot;h=re fs/heads/OPENLDAP_REL_ENG_2_4;sf=tgz> Configure & build. Execute the test suite (via make test) after it is built.On a CentOS 6.4 x86_64 VM I downloaded RE24 git rev f9e417a, did make test and scrolling back all tests were OK. Is there perhaps a summary file somewhere which contains the results of all tests? That would be a lot easier and quicker than scrolling back a zillion lines.If a test fails, the test suite will stop. ;)Most test suits work differently, and they write a summary line at the end
(like "# test suceeded, # tests failed, # test skipped")The OpenLDAP test suite's default behavior hasn't changed in 15 years. It was written for developers; developers should fix problems as soon as they are detected.
In recent releases, the behavior you describe was added. You enable it by setting the NOEXIT environment variable. Packagers tend to want this behavior. Note that the underlying assumption of the OpenLDAP Project is that we are developing source code and releasing it to be read by other developers. When we preface an announcement with "If you know how to build OpenLDAP manually" that should also mean, at the very least, "you are not afraid to read Makefiles and shell scripts" and thus there is no need to explain any of this.
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/