aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl/test/release_handler_SUITE.erl
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2013-04-15 14:54:38 +0200
committerSiri Hansen <[email protected]>2013-04-19 10:57:13 +0200
commit5228664f1fd41fa3c6e894dd0650d79d906f951b (patch)
tree609ff78bd346e96a1c161115b220595e61eaf746 /lib/sasl/test/release_handler_SUITE.erl
parent02e6d017104cdbd5cc8c4cf542b727ab621dad96 (diff)
downloadotp-5228664f1fd41fa3c6e894dd0650d79d906f951b.tar.gz
otp-5228664f1fd41fa3c6e894dd0650d79d906f951b.tar.bz2
otp-5228664f1fd41fa3c6e894dd0650d79d906f951b.zip
[common_test] Kill slave nodes after test cases in cover_SUITE
The test case cover_SUITE:slave_start_slave often fails on a test host (windows) due to a hanging node from an earlier test run. In the first test, the slave fails to start (boot_timeout?) and is never connected to the test node. The attempt at cleaning up used nodes() to find which slaves to kill - so in the case where the slave was never connected it was never killed. This is no changed so each slave is explicitly killed by name - no matter if it is pingable or not.
Diffstat (limited to 'lib/sasl/test/release_handler_SUITE.erl')
0 files changed, 0 insertions, 0 deletions