The autobuild test system (on sn-devel-144) has detected an intermittent failing test in the current master tree.
The autobuild log of the failure is available here: https://git.samba.org/autobuild.flakey.sn-devel-144/2018-10-06-0635/flakey.log The failure seems to be in the "samba-py3" suite, whose build logs are available here: https://git.samba.org/autobuild.flakey.sn-devel-144/2018-10-06-0635/samba-py3.stderr https://git.samba.org/autobuild.flakey.sn-devel-144/2018-10-06-0635/samba-py3.stdout The top commit at the time of the failure was: commit 6784ff24b8a31b9d597d24cab6e34feea2b83e29 Author: Martin Schwenke <[email protected]> Date: Fri Oct 5 14:04:18 2018 +1000 ctdbd_conn: Generalise inaccurate error message Seeing: ctdb_read_packet failed: Cannot allocate memory [..., 0] ../source3/lib/ctdbd_conn.c:121(cluster_fatal) cluster fatal event: ctdbd died The error is due to a memory allocation failure rather than ctdbd dying. However, the error message makes people wonder why ctdbd died. Another alternative would be to wrap cluster_fatal() and have the wrapper interpret the return value from ctdb_read_packet() to choose from a set of more precise messages to pass to cluster_fatal(). For a memory allocation it isn't strictly necessary to call cluster_fatal(), but all is probably lost and it is still probably better to try to exit cleanly as soon as possible instead of crashing somewhere. Signed-off-by: Martin Schwenke <[email protected]> Reviewed-by: Volker Lendecke <[email protected]> Autobuild-User(master): Volker Lendecke <[email protected]> Autobuild-Date(master): Fri Oct 5 16:16:29 CEST 2018 on sn-devel-144 and the last 50 lines of the stdout log were: [21(158)/75 at 3m58s] samba.tests.password_hash_fl2008.python3(ad_dc_ntvfs:local) [22(162)/75 at 4m0s] samba.tests.encrypted_secrets.python3(vampire_dc:local) [23(164)/75 at 4m38s] samba.tests.krb5_credentials.python3(ad_dc_ntvfs) [24(167)/75 at 4m40s] samba.tests.py_credentials.python3(ad_dc_ntvfs) [25(175)/75 at 4m45s] samba.tests.py_credentials.python3(vampire_dc) [26(183)/75 at 4m48s] samba.tests.py_credentials.python3(promoted_dc) [27(191)/75 at 5m34s] samba.tests.emulate.traffic.python3(ad_dc_ntvfs) [28(193)/75 at 5m35s] samba.tests.emulate.traffic_packet.python3(ad_dc_ntvfs) [29(282)/75 at 6m58s] samba.tests.blackbox.traffic_replay.python3(ad_dc_ntvfs) [30(288)/75 at 7m10s] samba.tests.blackbox.traffic_learner.python3(ad_dc_ntvfs) [31(290)/75 at 7m10s] samba.tests.blackbox.traffic_summary.python3(ad_dc_ntvfs) [32(290)/75 at 7m10s] samba.tests.blackbox.smbcontrol.python3(ad_dc_ntvfs:local) [33(292)/75 at 7m12s] samba.tests.blackbox.smbcontrol.python3(promoted_dc:local) [34(294)/75 at 7m13s] samba4.schemaInfo.python(ad_dc_ntvfs).python3(ad_dc_ntvfs) [35(296)/75 at 7m16s] samba.tests.dsdb_schema_attributes.python3(ad_dc_ntvfs:local) [36(302)/75 at 7m28s] samba4.drs.replica_sync_rodc.python(rodc).python3(rodc:local) [37(304)/75 at 8m13s] samba4.ldap.passwordsettings.python.python3(ad_dc_ntvfs) [38(316)/75 at 8m57s] samba4.tombstone_reanimation.python.python3(ad_dc_ntvfs) [39(328)/75 at 9m4s] samba.tests.upgradeprovisionneeddc.python3(ad_dc_ntvfs:local) [40(339)/75 at 9m6s] samba.tests.samba_tool.rodc.python3(rodc:local) [41(348)/75 at 9m36s] samba4.drs.ridalloc_exop.python(vampire_dc).python3(vampire_dc) [42(359)/75 at 12m18s] samba4.drs.samba_tool_drs.python(vampire_dc).python3(vampire_dc:local) [43(373)/75 at 13m59s] samba4.drs.samba_tool_drs_showrepl.python(vampire_dc).python3(vampire_dc:local) [44(377)/75 at 14m10s] samba4.drs.replica_sync.python(vampire_dc).python3(vampire_dc:local) UNEXPECTED(error): samba4.drs.replica_sync.python(vampire_dc).python3.replica_sync.DrsReplicaSyncTestCase.test_ReplConflictsRemoteWin(vampire_dc:local) REASON: Exception: Exception: Traceback (most recent call last): File "/memdisk/autobuild/fl/b3973521/samba-py3/source4/torture/drs/python/replica_sync.py", line 200, in test_ReplConflictsRemoteWin self.ou2 = self._create_ou(self.ldb_dc2, "OU=Test Remote Conflict") File "/memdisk/autobuild/fl/b3973521/samba-py3/source4/torture/drs/python/replica_sync.py", line 126, in _create_ou samdb.add_ldif(ldif) File "bin/python/samba/__init__.py", line 230, in add_ldif self.add(msg, controls) _ldb.LdbError: (68, 'LDAP error 68 LDAP_ENTRY_ALREADY_EXISTS - <Entry OU=Test Remote Conflict,OU=replica_sync7039577,DC=samba,DC=example,DC=com already exists> <>') FAILED (0 failures, 1 errors and 0 unexpected successes in 0 testsuites) A summary with detailed information can be found in: ./bin/ab/summary TOP 10 slowest tests samba4.drs.ridalloc_exop.python(vampire_dc).python3(vampire_dc) -> 162 samba4.drs.samba_tool_drs.python(vampire_dc).python3(vampire_dc:local) -> 101 samba.tests.emulate.traffic_packet.python3(ad_dc_ntvfs) -> 83 samba.tests.samba_tool.user.python3(ad_dc_ntvfs:local) -> 61 samba4.ldap.passwordsettings.python.python3(ad_dc_ntvfs) -> 44 samba.tests.samba_tool.user_wdigest.python3(ad_dc_ntvfs:local) -> 37 samba.tests.samba_tool.rodc.python3(rodc:local) -> 30 samba.tests.samba_tool.passwordsettings.python3(ad_dc_ntvfs:local) -> 25 samba.tests.samba_tool.computer.python3(ad_dc_ntvfs:local) -> 18 samba.tests.samba_tool.group.python3(ad_dc_ntvfs:local) -> 17 ERROR: test failed with exit code 1
