diff options
| author | Micael Karlberg <[email protected]> | 2019-06-13 11:51:42 +0200 |
|---|---|---|
| committer | Micael Karlberg <[email protected]> | 2019-06-17 10:24:43 +0200 |
| commit | a601b7989b90649acd4deb3e42a2105d4e145ca5 (patch) | |
| tree | a3ecf4f7a256d908501cdf67e33a02f13bb5ce79 /lib/mnesia | |
| parent | 447c50b21b35fa0fd35261d5add4f10b50cbda12 (diff) | |
| download | otp-a601b7989b90649acd4deb3e42a2105d4e145ca5.tar.gz otp-a601b7989b90649acd4deb3e42a2105d4e145ca5.tar.bz2 otp-a601b7989b90649acd4deb3e42a2105d4e145ca5.zip | |
[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.
Diffstat (limited to 'lib/mnesia')
0 files changed, 0 insertions, 0 deletions