Persistent failures of test050

Quanah Gibson-Mount <[email protected]>
Newsgroups gmane.network.openldap.devel
Message-ID <27B50DD13139F990BEC845BE@[192.168.1.39]>
I've noticed that when running test050 in a loop, it often fails, even 
after increasing the sleep timeout defaults.  Where it fails in the test is 
inconsistent and which servers differ is inconsistent as well. I'm 
concerned we may have a regression or perhaps long standing issue here that 
needs addressing.  I'll continue to investigate and see if I can get more 
details on what the issue(s) are.  In my latest run I see:

.....
Using ldapmodify to add/modify/delete entries from server 1...
  iteration 1
  iteration 2
  iteration 3
  iteration 4
  iteration 5
  iteration 6
  iteration 7
  iteration 8
  iteration 9
  iteration 10
Waiting 10 seconds for servers to resync...
Using ldapsearch to read all the entries from server 1...
Using ldapsearch to read all the entries from server 2...
Using ldapsearch to read all the entries from server 3...
Using ldapsearch to read all the entries from server 4...
Comparing retrieved entries from server 1 and server 2...
Comparing retrieved entries from server 1 and server 3...
test failed - server 1 and server 3 databases differ
Failed after 3 of 500 iterations


[build@freebsd12 ~/git/openldap-2-4/tests/testrun]$ diff -u server1.out 
server3.out
--- server1.out 2019-06-22 18:23:54.933600000 +0000
+++ server3.out 2019-06-22 18:23:55.049209000 +0000
@@ -1,3 +1,8 @@
+dn: cn=Add-Mod-Del,dc=example,dc=com
+cn: Add-Mod-Del
+objectClass: organizationalRole
+description: guinea pig
+
 dn: cn=All Staff,ou=Groups,dc=example,dc=com
 member: cn=Manager,dc=example,dc=com
 member: cn=Barbara Jensen,ou=Information Technology 
Division,ou=People,dc=exam


--Quanah


--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.