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.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/