autobuild: intermittent test failure detected
autobuild
autobuild at samba.org
Fri Oct 30 13:08:29 UTC 2015
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2015-10-30-1408/flakey.log
The samba build logs are available here:
http://git.samba.org/autobuild.flakey/2015-10-30-1408/samba.stderr
http://git.samba.org/autobuild.flakey/2015-10-30-1408/samba.stdout
The top commit at the time of the failure was:
commit d8f3b490bbb691c9916eed0df5b980c1aef23c85
Author: Amitay Isaacs <amitay at gmail.com>
Date: Fri Oct 30 14:25:50 2015 +1100
ctdb-banning: Do not set recovery mode to ACTIVE in daemon
When a node gets banned, it should go into recovery and freeze all
databases. We rely on the recovery daemon to detect the banned state
and put the node in recovery and freeze all databases.
Recent change in b4357a79d916b1f8ade8fa78563fbef0ce670aa9 took explicit
freezing out of banning code but left the setting of recovery mode
to ACTIVE. Recovery daemon will freeze databases only if the recovery
mode is NORMAL. Recovery mode set to ACTIVE is an indication that the
freeze has started.
Do not set the recovery mode to ACTIVE in banning. Let recovery daemon
take care of it.
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
Autobuild-User(master): Martin Schwenke <martins at samba.org>
Autobuild-Date(master): Fri Oct 30 10:32:38 CET 2015 on sn-devel-104
More information about the samba-cvs
mailing list