| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Make even deprecated test cases use the tc_try function (so that
all test cases look the same). Also make the skip reason for those
test cases be slightly more readable.
|
|
Make use of the tc_try function(s) in all "active" test cases.
|
|
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.
|
|
Make stopping the manager (the entire manager sup tree)
more easy. The function(s) for starting and stopping the
manager that exist in the snmpm module is (mostly) intended
for testing, making the stop function more "potent" is no
real problem (now any process not just the parent) can stop
the manager process tree.
|
|
We have seen one case when it takes unreasonably long time
to start the manager, which causes the test case (notify_started01)
to fail. We try to monitor the start, and if it takes to long
a time, we instead skip.
|
|
|
|
|
|
The function 'snmp:print_version_info/0' which prints
various (version) info, attempted to extract the
"compile time" of each module in the snmp app.
This info used to be availabe in the module_info of
each module, but has been removed (a "long" time ago).
This resulted in a pointless "Not Found" beeing printed.
This has now been removed from the into printed.
OTP-15330
|
|
|
|
OTP-15932
|
|
|
|
We have hosts (mostly *very* slooow VMs) that can timeout
anything. Since we are basically testing communication,
we therefor must check for system events at every failure.
Grrr!
|
|
Try to detect if the test case function skip's,
end re-exit so that "eventually" the test case
runner detects it in turn re-exit...#@!!£##!...
|
|
A test run where the node died after a series of "busy dist port"
events and then the node died which caused the process that ran
the test case to crash with reason = noconnection. And since this
was a "permanent" node, the remaining test cases then crashed.
Again, this has nothing to do with snmp or its test suites.
|
|
A very simple way to calculate how long the request timeout
shall be. Previously it was simply a constant (3.5 seconds).
We assume that the number of schedulers matters...
|
|
We maybe needs to throw the skip when we detect system events.
|
|
Warning for some functions "for no reason" (obviously
there is a reason, but I have to dig deeeep to find it).
Also warnings for stuff there is no way to type today
(for instance, improper lists).
OTP-15932
|
|
Also found and corrected some (apparently minor) bugs.
OTP-15932
|
|
Changes to satisfy dialyzer. Including changing the definition
of some of the behaviours (use the '-callback' attribute instead
of an explicit behaviour_info/1 function).
Also found and corrected some (apparently minor) bugs.
OTP-15932
|
|
Changes to satisfy dialyzer. Including changing the definition
of the snmpm_network_interface behaviour (use the '-callback'
attribute instead of an explicit behaviour_info/1 function).
OTP-15932
|
|
Make target (for running dialyzer on snmp), os usage
and a minor snmp_log ("future proofing").
OTP-15932
|
|
|
|
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.
|
|
On solaris 5.11 (actually OpenIndiana Hipster) the arguments
for (some of) the netsnmp programs differ from what is used
in our test suite.
Added actual checks for *one of* the failures, which is
indicated with the printout "illegal option". In those cases
the test case is instead skipped.
|
|
When a manager request timeout occurs (the manager sends
a request to the agent but does not receive a reply in time),
we now check if there has been any system monitor events,
and if so we instead skip's the test case.
|
|
We have experienced intermittent failures of random test cases
on slow VMs. In order to get more info about the system, we
use system monitor to collect info. We have one global monitor
system, and one local monitor on each node. Each local monitor
report to the global, which in turn prints a message.
|
|
Add verbosity printouts after a set operation. Both
for a successful and a failed set.
On one of our test hosts (a VM running an old gento),
it looked like an ets or dets insert hangs. But since
we only have a printout directly before, we can't
tell for sure what happens.
OTP-15764
|
|
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
|
|
Replaced the monitor (to the tc runner process) with
a link. The point is that if the test case "stalls",
the ts (ct) framework shall kill it (with the test case
process).
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
|
|
OTP-15764
|
|
Use of the deprecated module random has been replaced
by the module rand.
OTP-15331
|
|
Removed the use of the deprecated erlang:stacktrace() function.
Instead make use of the 'catch Class:Error:Stacktrace' feature.
OTP-15332
|
|
|
|
This reverts commit 425889ba69b69a9b6fb14bfbef121d51b78e853a.
|
|
|
|
|
|
* maint:
Updated OTP version
Prepare release
|
|
* maint-20:
Updated OTP version
Prepare release
# Conflicts:
# OTP_VERSION
# erts/doc/src/notes.xml
# erts/vsn.mk
# lib/common_test/doc/src/notes.xml
# lib/common_test/vsn.mk
# lib/erl_interface/doc/src/notes.xml
# lib/erl_interface/vsn.mk
# lib/snmp/doc/src/notes.xml
# lib/snmp/vsn.mk
# lib/ssh/doc/src/notes.xml
# lib/ssh/vsn.mk
# lib/tools/doc/src/notes.xml
# lib/tools/vsn.mk
# make/otp_version_tickets
# otp_versions.table
|
|
|
|
There no timestamp type in os (but there is in erlang).
|
|
|
|
|
|
For the notify_started02 test case we (now) try estimate how
long we should wait for completion (based on the time of the
first iteration). On slow machines, it takes longer to start and
stop the manager, so adjust the total timeout accordingly.
|
|
|
