solaris 8 make test failures 9/44

[email protected]
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
The ./configure and make of net-snmp 5.1.3.1 went ok, but make test 
yeilded the following:

----snip-----
if test "x/usr/bin/perl" != "x" ; then \
  /usr/bin/perl -p -e 's%^#!.*/perl.*%#!/usr/bin/perl%; 
s#/usr/local/share#/usr/local/share#g; 
s#/usr/local/etc/snmp##g' ./traptoemail > traptoemail.made; \
else \
  touch traptoemail.made; \
        fi
making all in /u01/patches/dev/net-snmp-5.1.3.1/mibs
chmod a+x net-snmp-config
touch net-snmp-config-x
(root@devserv)-> make test
making all in /u01/patches/dev/net-snmp-5.1.3.1/snmplib
making all in /u01/patches/dev/net-snmp-5.1.3.1/agent
making all in /u01/patches/dev/net-snmp-5.1.3.1/agent/helpers
making all in /u01/patches/dev/net-snmp-5.1.3.1/agent/mibgroup
making all in /u01/patches/dev/net-snmp-5.1.3.1/apps
making all in /u01/patches/dev/net-snmp-5.1.3.1/apps/snmpnetstat
making all in /u01/patches/dev/net-snmp-5.1.3.1/man
making all in /u01/patches/dev/net-snmp-5.1.3.1/local
making all in /u01/patches/dev/net-snmp-5.1.3.1/mibs
for i in testing ; do   \
           ( cd $i ; make ) ;           \
           if test $? != 0 ; then \
              exit 1 ; \
           fi  \
done
( cd testing; make test )
./RUNTESTS -a -D `pwd`/.. 
1: testing SNMPv1 support... Killed
Killed
(no pid file(s) found) FAIL
2: testing SNMPv2c get of system.sysUpTime.0... Killed
Killed
(no pid file(s) found) FAIL
3: testing SNMPv2c getnext of system.sysUpTime... Killed
Killed
(no pid file(s) found) FAIL
4: testing SNMPv2 bulkget of system components... Killed
Killed
(no pid file(s) found) FAIL
5: testing for failure of SNMPv2c get with wrong community... Killed
Killed
(no pid file(s) found) FAIL
6: testing for failure of SNMPv2c get against SNMPv1 agent... Killed
Killed
(no pid file(s) found) FAIL
7: testing for failure of SNMPv1 get against SNMPv2c agent... Killed
Killed
(no pid file(s) found) FAIL
8: testing SNMPv2c get of system.sysUpTime.1... Killed
Killed
(no pid file(s) found) FAIL
9: testing SNMPv3 get using initial of .1.3.6.1.2.1.1.3.0... Killed
Killed
(no pid file(s) found) FAIL
10: testing SNMPv3 getnext using initial of .1.3.6.1.2.1.1.3.0... Killed
Killed
(no pid file(s) found) FAIL
11: testing SNMPv3 bulkget of system... Killed
Killed
(no pid file(s) found) FAIL
12: testing SNMPv3 get using initial/MD5 of .1.3.6.1.2.1.1.3.0... Killed
Killed
(no pid file(s) found) FAIL
13: testing SNMPv3 get using initial/MD5DES of .1.3.6.1.2.1.1.3.0... 
Killed
Killed
(no pid file(s) found) FAIL
14: testing SNMPv3 get using templateSHA/SHA of .1.3.6.1.2.1.1.3.0... 
Killed
Killed
(no pid file(s) found) FAIL
15: testing SNMPv3 get using templateSHA/MD5DES 
of .1.3.6.1.2.1.1.3.0... Killed
Killed
(no pid file(s) found) FAIL
16: testing for failure of SNMPv3 get using unknown user.... Killed
Killed
(no pid file(s) found) FAIL
17: testing SNMPv3 user creation and usage using snmpusm... Killed
Killed
(no pid file(s) found) FAIL
18: testing SNMPv3 informs received and sent by tools... Killed
Killed
(no pid file(s) found) FAIL
19: testing SNMPv3 traps received and sent by tools... Killed
Killed
(no pid file(s) found) FAIL
20: testing SNMPv2c traps received and sent by tools... Killed
Killed
(no pid file(s) found) FAIL
21: testing SNMPv2c informs received and sent by tools... Killed
Killed
(no pid file(s) found) FAIL
22: testing snmpv1 traps are sent by snmpd API... SKIPPED
23: testing snmpv2c traps are sent by snmpd API... SKIPPED
24: testing snmpv1 traps are sent by snmpd without notification mib 
support... SKIPPED
25: testing snmpv2c traps are sent by snmpd without notification mib 
support... SKIPPED
26: testing authentication failure traps are sent by snmpd... Killed
Killed
Killed
(no pid file(s) found) FAIL
27: testing that the agent responds properly to a kill -HUP... Killed
cat: cannot open /tmp/snmp-test-27-26941/snmpd.pid
Killed
(no pid file(s) found) FAIL
28: testing AgentX GET support... Killed
Killed
(no pid file(s) found) FAIL
29: testing AgentX SET support... Killed
Killed
(no pid file(s) found) FAIL
30: testing AgentX illegal SET handling support... Killed
Killed
(no pid file(s) found) FAIL
31: testing AgentX trap sending support... SKIPPED
32: testing Proxy GET support... Killed
Killed
Killed
(no pid file(s) found) FAIL
33: testing Proxy SET support... Killed
Killed
Killed
(no pid file(s) found) FAIL
34: testing Proxy illegal SET handling support... Killed
Killed
Killed
Killed
(no pid file(s) found) FAIL
35: testing SNMPv1 vacm acceptance support... Killed
Killed
(no pid file(s) found) FAIL
36: testing SNMPv2 vacm acceptance support... Killed
Killed
(no pid file(s) found) FAIL
37: testing SNMPv3 vacm acceptance support... Killed
Killed
(no pid file(s) found) FAIL
38: testing SNMPv1 vacm denial support... Killed
Killed
(no pid file(s) found) FAIL
39: testing SNMPv2 vacm denial support... Killed
Killed
(no pid file(s) found) FAIL
40: testing SNMPv3 vacm denial support... Killed
Killed
(no pid file(s) found) FAIL
41: testing 1st CPU on Solaris using HOST-RESOURCES... SKIPPED
42: testing initial load device on Solaris using HOST-RESOURCES... 
SKIPPED
43: testing uptime using HOST-RESOURCES... SKIPPED
44: testing swap on Solaris using HOST-RESOURCES... SKIPPED
Summary: 9 / 44 succeeded.
*** Error code 35
make: Fatal error: Command failed for target `test'
Current working directory /u01/patches/dev/net-snmp-5.1.3.1/testing
*** Error code 1
make: Fatal error: Command failed for target `test'



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.