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-1833/flakey.log The failure seems to be in the "ctdb" suite, whose build logs are available here: https://git.samba.org/autobuild.flakey.sn-devel-144/2018-10-06-1833/ctdb.stderr https://git.samba.org/autobuild.flakey.sn-devel-144/2018-10-06-1833/ctdb.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: PASSED tests/tool/ctdb.unban.003.sh PASSED tests/tool/ctdb.uptime.001.sh PASSED tests/tool/ctdb.writekey.001.sh PASSED tests/simple/00_ctdb_init.sh PASSED tests/simple/00_ctdb_onnode.sh PASSED tests/simple/01_ctdb_version.sh PASSED tests/simple/02_ctdb_listvars.sh PASSED tests/simple/03_ctdb_getvar.sh PASSED tests/simple/04_ctdb_setvar.sh PASSED tests/simple/05_ctdb_listnodes.sh PASSED tests/simple/06_ctdb_getpid.sh PASSED tests/simple/07_ctdb_process_exists.sh PASSED tests/simple/08_ctdb_isnotrecmaster.sh PASSED tests/simple/09_ctdb_ping.sh PASSED tests/simple/11_ctdb_ip.sh PASSED tests/simple/12_ctdb_getdebug.sh PASSED tests/simple/13_ctdb_setdebug.sh PASSED tests/simple/14_ctdb_statistics.sh PASSED tests/simple/15_ctdb_statisticsreset.sh PASSED tests/simple/16_ctdb_config_add_ip.sh PASSED tests/simple/17_ctdb_config_delete_ip.sh PASSED tests/simple/18_ctdb_reloadips.sh PASSED tests/simple/19_ip_takeover_noop.sh PASSED tests/simple/20_delip_iface_gc.sh PASSED tests/simple/21_ctdb_attach.sh PASSED tests/simple/23_ctdb_moveip.sh PASSED tests/simple/24_ctdb_getdbmap.sh PASSED tests/simple/25_dumpmemory.sh PASSED tests/simple/26_ctdb_config_check_error_on_unreachable_ctdb.sh PASSED tests/simple/27_ctdb_detach.sh PASSED tests/simple/28_zero_eventscripts.sh PASSED tests/simple/31_ctdb_disable.sh PASSED tests/simple/32_ctdb_enable.sh PASSED tests/simple/35_ctdb_getreclock.sh PASSED tests/simple/41_ctdb_stop.sh PASSED tests/simple/42_ctdb_continue.sh PASSED tests/simple/43_stop_recmaster_yield.sh PASSED tests/simple/51_message_ring.sh PASSED tests/simple/52_fetch_ring.sh PASSED tests/simple/53_transaction_loop.sh PASSED tests/simple/54_transaction_loop_recovery.sh PASSED tests/simple/55_ctdb_ptrans.sh PASSED tests/simple/56_replicated_transaction_recovery.sh PASSED tests/simple/58_ctdb_restoredb.sh *FAILED* tests/simple/60_recoverd_missing_ip.sh 519/520 tests passed Removing TEST_VAR_DIR=/memdisk/autobuild/fl/b1951461/ctdb/ctdb/tests/var autotest exited with exit status 1
