Closed Bug 75406 Opened 23 years ago Closed 23 years ago

stresstest failure not recognized by QA

Categories

(NSS :: Tools, defect)

3.2.1
x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sonja.mirtitsch, Assigned: sonja.mirtitsch)

Details

assigning to myself, I still need to find out if strsclnt returns 0 on failure
or there is a bug in the scripts

The tests failed on the new PC, no NSS QA has ever passed on this PC before (I
will file a seperate bug on the gethostbyname failure)

ssl.sh: SSL Stress Test ===============================
ssl.sh: Stress SSL2 RC4 128 with MD5 ----
selfserv -p 8443 -d ../server -n pc592997.red.iplanet.com \
         -w nss   -i ../tests_pid.772  & selfserv started at Tue Apr 10 01:16:51
PDT 2001
tstclnt -p 8443 -h pc592997 -q -d . <
W:/nss/nsstip/builds/20010410.1/blowfish_NT4.0_Win95/mozilla/security/nss/tests/ssl/sslreq.txt

strsclnt -p 8443 -d . -w nss -c 1000 -C A  \
         pc592997.red.iplanet.com
strsclnt started at Tue Apr 10 01:16:55 PDT 2001
strsclnt: PR_GetHostByName returned error -5973:
A directory lookup on a network address has failed.
strsclnt completed at Tue Apr 10 01:16:57 PDT 2001
ssl.sh: Stress SSL3 RC4 128 with MD5 ----
selfserv -p 8443 -d ../server -n pc592997.red.iplanet.com \
         -w nss   -i ../tests_pid.772  & selfserv started at Tue Apr 10 01:16:58
PDT 2001
tstclnt -p 8443 -h pc592997 -q -d . <
W:/nss/nsstip/builds/20010410.1/blowfish_NT4.0_Win95/mozilla/security/nss/tests/ssl/sslreq.txt

strsclnt -p 8443 -d . -w nss -c 1000 -C c  \
         pc592997.red.iplanet.com
strsclnt started at Tue Apr 10 01:17:01 PDT 2001
strsclnt: PR_GetHostByName returned error -5973:
A directory lookup on a network address has failed.
strsclnt completed at Tue Apr 10 01:17:03 PDT 2001
It was a bug in the script.
The gethostbyname problem was resolved by changing the PC's network configuration
fix to ssl.sh checked in
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.