diff options
| author |  Thomas Guyot-Sionnest <dermoth@aei.ca>
| 2011-01-05 23:09:54 -0500 |
|---|---|---|
| committer | Thomas Guyot-Sionnest <dermoth@aei.ca>
| 2011-01-05 23:09:54 -0500 |
| commit | ae2a66913706e4cb3fc870485abe34c0f3696124 (patch) | |
| tree | ce6cc70005c6dfb60981aff4626d8d6fa4db2fcb /plugins/t | |
| parent | fdd0028be1e33f540b0f24f445eaa0301a55b7d1 (diff) | |
| download | monitoring-plugins-ae2a66913706e4cb3fc870485abe34c0f3696124.tar.gz | |
Test updates...
1. Timetick test could fail with uptime > 115 days. Thresholds are
double type, so it's safe to put a large number even for 32bit systems.
2. Add a test based on an invalid bug report, worthy anyway.
Diffstat (limited to 'plugins/t')
| -rw-r--r-- | plugins/t/check_snmp.t | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/plugins/t/check_snmp.t b/plugins/t/check_snmp.t index 25a2999d..04bf500b 100644 --- a/plugins/t/check_snmp.t +++ b/plugins/t/check_snmp.t @@ -124,7 +124,7 @@ SKIP: { cmp_ok( $res->return_code, '==', 0, "Skipping all thresholds"); like($res->output, '/^SNMP OK - \d+ \w+ \d+\s.*$/', "Skipping all thresholds, result printed rather than parsed"); - $res = NPTest->testCmd( "./check_snmp -H $host_snmp -C $snmp_community -o system.sysUpTime.0 -c 1000000000: -u '1/100 sec'"); + $res = NPTest->testCmd( "./check_snmp -H $host_snmp -C $snmp_community -o system.sysUpTime.0 -c 1000000000000: -u '1/100 sec'"); cmp_ok( $res->return_code, '==', 2, "Timetick used as a threshold"); like($res->output, '/^SNMP CRITICAL - \*\d+\* 1\/100 sec.*$/', "Timetick used as a threshold, parsed as numeric"); |