aboutsummaryrefslogtreecommitdiffstats
path: root/lib/snmp/test
AgeCommit message (Collapse)Author
2019-07-08Merge branch 'bmk/snmp/20190607/discover_slooow_vm_issues' into maintMicael Karlberg
2019-07-02[snmp|agent|test] Add another "skip point"Micael Karlberg
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!
2019-06-27[snmp|agent|test] Add another "skip point"Micael Karlberg
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...#@!!£##!...
2019-06-27[snmp|agent|test] Add another "skip point"Micael Karlberg
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.
2019-06-27[snmp|agent|test] Try to figure out how "fast" a machine isMicael Karlberg
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...
2019-06-27[snmp|agent|test] (maybe) Needs to throw the skipMicael Karlberg
We maybe needs to throw the skip when we detect system events.
2019-06-24Merge branch 'bmk/snmp/20190524/ipv6_issues/OTP-15764' into maintMicael Karlberg
2019-06-17[snmp|manager|test] Problems starting (slave) nodesMicael Karlberg
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.
2019-06-14[snmp|test] Issues with netsnmp test on Solaris 5.11Micael Karlberg
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.
2019-06-12[snmp|agent|test] Attempt to skip when system events happenMicael Karlberg
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.
2019-06-07[snmp|test] Use system monitor to discover slow VM issuesMicael Karlberg
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.
2019-05-29[snmp|test] Improved IPv6 test checksMicael Karlberg
Improve the checks for if/when we shall run the IPv6 test cases. OTP-15764
2019-05-28[snmp|test] Maybe skipable (IPv6) groupsMicael Karlberg
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
2019-05-28[snmp|test] Replaced monitor with linkMicael Karlberg
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
2019-05-28[snmp|test] Improve the test case startMicael Karlberg
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
2019-05-28[snmp|test] Add more printouts to understand IPv6 issuesMicael Karlberg
OTP-15764
2019-05-22[snmp] Replaced usage of random with randMicael Karlberg
Use of the deprecated module random has been replaced by the module rand. OTP-15331
2019-04-15Merge branch 'bmk/snmp/agent/20190411/test_suite_improvements'Micael Karlberg
2019-04-15Merge branch 'bmk/snmp/manager/20190410/test_suite_tweaking'Micael Karlberg
2019-04-12[snmp|manager|test] Try to estimate appropriate timeouts for start/stopMicael Karlberg
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.
2019-04-11[snmp|agent|test] Test case info and cleanupMicael Karlberg
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).
2019-04-11[snmp|agent|test] Timestamps and test managerMicael Karlberg
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.
2019-04-11[snmp|agent|test] More test tweakingMicael Karlberg
Improved test printouts (more with timestamps), also fixed the printouts of the (fake) local-db start result printout. Also updated the copyright end-dates.
2019-04-11[snmp|agent|test] The agent test local-db may already be startedMicael Karlberg
Handle when the agent test manager starts the fake local-db and that process is already running (for some reason).
2019-04-11[snmp|agent|test] Agent test manager start fixMicael Karlberg
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).
2019-04-11[snmp|agent|test] Improve the EXPECT printoutsMicael Karlberg
The EXPECT printouts has been improved. Partly by including a timestamp.
2019-04-11[snmp|agent|test] Tweaked the (agent) test managerMicael Karlberg
The test manager used in the agent tests has been tweaked in order to increase the readability (both of the code and the output).
2019-04-11[snmp|agent|test] Some minor tweaking of (agent) test suiteMicael Karlberg
Improved the test manager printouts to make it easier to diagnose problems...
2019-04-11Merge branch 'maint'Micael Karlberg
2019-04-11Merge branch 'bmk/snmp/20190328/get_mechanism/OTP-15691' into maintMicael Karlberg
2019-04-10[snmp|manager|test] Finding address of localhostMicael Karlberg
Some simple tweaking to find the "proper" address to localhost (to make test suite work in the office environment).
2019-04-10[snmp|manager|test] Improve init_per_testcaseMicael Karlberg
Try to handle "failures" during init_per_testcase such that if they are either throw or exit, then they are transformed into a skip.
2019-03-28[snmp|manager|test] Add bind_to for agentsMicael Karlberg
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.
2019-03-28[snmp|agent] Add the net-if data (Extra) argument to get-callbacksMicael Karlberg
Added the Extra (net-if data) argument to all the get- mechanism callback functions. OTP-15691
2019-03-28[snmp|agent] Add the default get-mechanism module snmpa_getMicael Karlberg
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
2019-03-28[snmp|compiler|test] OTP-Mibs cleanupMicael Karlberg
Removed the last vestiges of the otp_mibs app from the compiler test suite (was still trying to use MIBs from otp_mibs).
2018-09-27[snmp] Cleanup before removing the otp_mibs appMicael Karlberg
OTP-14984
2018-09-21Merge branch 'maint'Henrik Nord
2018-09-21Update copyright yearHenrik Nord
2018-07-27Change "can not" into "cannot"Raimo Niskanen
I did not find any legitimate use of "can not", however skipped changing e.g RFCs archived in the source tree.
2018-06-11Add test caseRaimo Niskanen
2018-06-11Add test caseRaimo Niskanen
2017-11-09snmp: Correct netsnmp arglist and check for usable netsnmpIngela Anderton Andin
2017-10-27snmp: Add crypto precondition testIngela Anderton Andin
2017-07-28Process augments in pass after definitionsRaimo Niskanen
2017-06-14Update copyright yearHans Nilsson
2017-02-14Fixed typos in lib/snmpAndrew Dryga
2017-01-13Test enum refinement MIBRaimo Niskanen
2016-09-12Merge branch 'ingela/snmp/ipv6-tests' into maintIngela Anderton Andin
* ingela/snmp/ipv6-tests: snmp: Use ipv6 common test configuration check
2016-09-12snmp: Use ipv6 common test configuration checkIngela Anderton Andin
The test for ipv6 could return false positives which resulted in failing test cases due lack of full ipv6 support.It could be nice with a working run-time check but this will do for now.