From a601b7989b90649acd4deb3e42a2105d4e145ca5 Mon Sep 17 00:00:00 2001 From: Micael Karlberg Date: Thu, 13 Jun 2019 11:51:42 +0200 Subject: [snmp|manager|test] Problems starting (slave) nodes When we fail to start a (slave) node with reason timeout, its possible that it actually succeeded, which will cause the following test case(s) init to fail (with 'already started', since it which also try to start this node). But since we don't know if we get this because for this reason or because the previous test case failed to clean up after itself, we cannot assume that the state of the node is ok (and therefor use it). So, we attempt to stop it, and try start it again (*one* time). This has been observed on one (slooow) VM host. --- lib/snmp/test/snmp_test_lib.hrl | 1 + 1 file changed, 1 insertion(+) (limited to 'lib/snmp/test/snmp_test_lib.hrl') diff --git a/lib/snmp/test/snmp_test_lib.hrl b/lib/snmp/test/snmp_test_lib.hrl index c66602b779..99b86a928c 100644 --- a/lib/snmp/test/snmp_test_lib.hrl +++ b/lib/snmp/test/snmp_test_lib.hrl @@ -92,6 +92,7 @@ -define(LNODES(), snmp_test_lib:local_nodes()). -define(NODES(H), snmp_test_lib:nodes_on(H)). -define(START_NODE(N,A), snmp_test_lib:start_node(N,A)). +-define(STOP_NODE(N), snmp_test_lib:stop_node(N)). %% - Application and Crypto utility macros - -- cgit v1.2.3