Age | Commit message (Collapse) | Author |
|
Add a utility function, tc_try/2,3, for running test cases
in a uniform way.
|
|
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.
|
|
Improve the checks for if/when we shall run the IPv6
test cases.
OTP-15764
|
|
The function used by "all" the agent test cases to
actually run the operations have been improved.
There was previously very little monitoring of the
result. Have added some (minor) checks, both before
trying to running the test case, and "during".
Such as, is the node we attempt to use actually alive.
Then, when we spawn the test case runner process on
the (remote) node, make it report back before trying
to run the actuall test case (so we know that the spawn
worked.
Also added a monitor of the process, so that we will
detect fatal errors.
OTP-15764
|
|
Improved test printouts (more with timestamps), also
fixed the printouts of the (fake) local-db start
result printout.
Also updated the copyright end-dates.
|
|
|
|
|
|
|
|
|