Paul B. Henson wrote:
From: Howard Chu Sent: Friday, August 4, 2017 4:23 AM
Nice work, thanks for the update.
So 10 of the mdb tests ended up failing; a couple because slapd failed to start, a bunch because ldapadd failed, and one because the script that evidently was executable per the -x test moments before suddenly wasn't found? There doesn't seem to be any log info or other remnants of the tests left over once they are done running to determine why they failed? Unless I missed something; what does one do to check on a test to see why it failed? Thanks…
By default, all test output is in the testrun directory.
On Sat, Aug 05, 2017 at 11:25:48AM +0100, Howard Chu wrote:
By default, all test output is in the testrun directory.
Ah, I see; there's only the output from the most recent test. I had set NOEXIT to run all the tests with the intention of looking over all the failures at once rather than one at a time; it seems my attempt at efficiency backfired :). Looks like most of the slapd not starting failures are issues with my tweak to the conf.sh script not enabling writemap in all the test configs, I guess I'll have to make that kludge more complicated.
Thanks...
openldap-technical@openldap.org
-
Howard Chu -
Paul B. Henson