| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
|
|
1) A test case failed due to the times retreived by
get(snmpEngineTime) reported to large time diffs
(this is basically a sanity check).
Added some more info about time(s) to see if there
are some "gaps" somewhere.
The problem occurred on a slow Virtial Machine.
2) A previous (failing) test case failed to cleanup after
itself (see above), which caused later test cases to fail.
Specifically, the app top supervisor was not terminated,
which caused the start agent function to fail (basically
already_started).
|
|
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.
|
|
Handle when the agent test manager starts the fake local-db
and that process is already running (for some reason).
|
|
The agent test manager had a bug during start that could
potentially cause deadlock, but atleast could cause test
cases to fail because of timeouts. The test manager
(actually the "packet server") used proc_lib to start the
process but it called the init_ack function before the init
was actually complete. This was only a problem for v3 cases
(where it did a bunch of further inits, including starting
the local-db process).
Also did debug/verbosity tweaking. Added a bunch of debug
(verbosity) printouts for the agent test manager "packet server"
during v3 init. Also made sure we could distinguish the
"normal" local-db from the one used by the test manager
(this is done by using a new short-name).
|
|
The EXPECT printouts has been improved. Partly by
including a timestamp.
|
|
Improve debug (verbose) printouts when a get/get-next/get-bulk/set
request fails (first by printing at level log instead of trace
and secondly by also printing the original operation result
when the operation fails).
|
|
The test manager used in the agent tests has been tweaked
in order to increase the readability (both of the code
and the output).
|
|
Improved the test manager printouts to make it easier to
diagnose problems...
|
|
|
|
|
|
Some simple tweaking to find the "proper" address
to localhost (to make test suite work in the office
environment).
|
|
Try to handle "failures" during init_per_testcase such that
if they are either throw or exit, then they are transformed
into a skip.
|
|
On some linux platforms "they" add a 127.0.1.1
in the hosts file, wich can cause problems for
some (manager) test cases. So, just to be on
the safe side, make sure we bind to the configured
address.
Note that this has nothing to do with the current
issue.
|
|
Added VMODULE for the two new modules.
Also, improved some verbose printouts.
OTP-15691
|
|
Added the Extra (net-if data) argument to all the get-
mechanism callback functions.
OTP-15691
|
|
Added the snmpa_get module as the default get-mechanism
for the agent.
This has been done by simply moving the do_get, do_get_next
and do_get_bulk functions from the snmpa_agent module.
Some functions where also moved into the lib module (with
the idea of beeing more generally useful).
OTP-15691
|
|
Added preliminary version of the get-mechanism behaviour.
OTP-15691
|
|
Add/update and export some useful types.
OTP-15691
|
|
Fixed the build order. Some of the mib modules export types
used by other modules, so build them (the mib-modules) first
(after snmpa).
OTP-15691
|
|
Also streamlined the config storage. And corrected
the store of the set_mechanism (in the snmp_agent_table).
This is only used for debugging, but just the same.
OTP-15691
|
|
Removed the last vestiges of the otp_mibs app from the
compiler test suite (was still trying to use MIBs from
otp_mibs).
|
|
This reverts commit 0118046f9bda8dcf3594184fa439b79267db8017.
|
|
|
|
This reverts commit df130102cdeca8d35fec95a0c926fd1cfec54eab.
|
|
|
|
|
|
|
|
introduced after OTP_R13B03.
|
|
|
|
OTP-14984
|
|
Moved the (final) OTP-TC mib from the otp_mibs app to the snmp app.
Also basic update to the system (oam) documentation.
OTP-14984
|
|
OTP-14984
|
|
|
|
|
|
|
|
|
|
|
