| Age | Commit message (Collapse) | Author |
|---|
|
Add a utility function, tc_try/2,3, for running test cases
in a uniform way.
|
|
The (second) notify test case had a faulty "condition" test
(which skipped the case in all cases except when it was
supposed to be skipped :)
Also, the test start and stop of the manager during the
test case has been adjusted. We try to keep track of how
long time each start and stop takes. And also, if they takes
to long, we skip the case.
|
|
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
|
|
Add an "os test" to the IPv6 group init.
On "old" version of darwin (9.8.0) its
simply to messy to figure out our IPv6
address, so its better to simply skip the
IPv6 tests on those machines.
OTP-15764
|
|
|
|
Added common (formated) timestamp function(s). Made use of
these in the verbosity module (for debug printouts) and in
the test suite(s).
I also *think* I found the cause for some if the test case
failures (timeouts).
For v3 (agent) test cases the test manager makes use of parts
of the agent code: snmp_framework_mib and snmp_user_based_sm_mib.
And since they store their data in snmpa_local_db, that also
needs to be running.
And this was the problem (I think). On some (slow) machines,
the snmpa_local_db process from the *previous* test case
might still be running when the we tried to start it. That meant
that no new snmpa_local_db was started. Instead the old one,
still running but terminating, was retain. For a while. Until
it actually finally stopped. So the next operation towards
snmpa_local_db, insert, simply hanged until the process
terminated.
This in combination with the fact that the packet server process,
which was started using proc_lib, previously called init_ack
before this init was actually done, could actually start and then
at a much later time hang because some operation timed out
(the packet server was hanging).
Yuckety yuck-yuck.
|
|
Improved test printouts (more with timestamps), also
fixed the printouts of the (fake) local-db start
result printout.
Also updated the copyright end-dates.
|
|
Some simple tweaking to find the "proper" address
to localhost (to make test suite work in the office
environment).
|
|
|
|
|
|
|
|
|
|
Test suite utility function for verifying crypto support
updated to use new crypto interface.
OTP-11009
|
|
Updated manager test suite to use only the api. The test cases
that tested the old api (01), are now skipped.
OTP-10027
|
|
|
|
bmk/snmp/snmp422_integration/r15
Conflicts:
lib/snmp/test/snmp_app_test.erl
|
|
OTP-9940
|
|
Updated manager test suite with groups that
tests the new net-if module, snmpm_net_if_mt.
Also fixed the suite, group and test-case init
functions for a number of sub-suites.
OTP-9876
|
|
OTP-9851
|
|
|
|
|
