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…
test020-proxycache: Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start...
test049-sync-config: Adding schema and databases on provider... ldapadd failed for database config (80)!
test050-syncrepl-multimaster: Adding schema and databases on server 1... ldapadd failed for database config (80)!
test052-memberof: Running ldapadd to build slapd config database... ldapadd failed (80)!
test057-memberof-refint: Running ldapadd to build slapd config database... ldapadd failed (80)!
test058-syncrepl-asymmetric: Adding database config on central master... ldapadd failed for central master database config (80)!
test059-slave-config: Adding schema and databases on provider... ldapadd failed for database config (80)!
test061-syncreplication-initiation: Adding database configuration on ldap://localhost:9011/ ldapadd failed (80)!
test063-delta-multimaster: Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start...
test064-constraint: /usr/obj/ports/openldap-2.4.44/openldap-2.4.44/tests/scripts/all[91]: /usr/obj/ports/openldap-2.4.44/openldap-2.4.44/tests/scripts/test064-constraint: No such file or directory