RSA Enc /Decrypt ops failed on 20021008.1 Win2000 OPT build

RESOLVED DUPLICATE of bug 82393

Status

NSS
Libraries
P1
normal
RESOLVED DUPLICATE of bug 82393
15 years ago
15 years ago

People

(Reporter: Bishakha Banerjee, Assigned: Wan-Teh Chang)

Tracking

x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

15 years ago
QA on 'miller', a Win 2000 machine, shows failures in the Cipher tests section -
for the RSA Encrypt and Decrypt operations.

These failures are not reflected on the build and QA at Sun.  There have been no
checkins since Sonja did her nightly builds at Sun and our Win builds were
respun this afternoon.

These are excerpts from the log file:
=======================================================
tstclnt -p 8443 -h MILLER -q -d . <
W:/nss/nss322/builds/20010820.1/blowfish_NT4.0_Win95/mozilla/security/nss/tests/ssl/sslreq.txt

tstclnt -p 8443 -h MILLER -f -d . -T -n TestUser -w bogus \
        <
W:/nss/nss322/builds/20010820.1/blowfish_NT4.0_Win95/mozilla/security/nss/tests/ssl/sslreq.txt
tstclnt: write to SSL socket failed
[12] + Done(134) ?
  968	Abort	tstclnt
ssl.sh: WARNING! Testclient returned 134, expect 
             254 (no error as tmp workaround)

==========================================================================

cipher.sh: RSA Encrypt --------------------------------
bltest -T -m rsa -E -d .
[1] + Done(139) ?
  976	Segmentation violation	bltest
cipher.sh: RSA Decrypt --------------------------------
bltest -T -m rsa -D -d .
[1] + Done(139) ?
  976	Segmentation violation	bltest
(Reporter)

Comment 1

15 years ago
Created attachment 102269 [details]
results.html file

The failures were in the BC section. I'll change the Summary to reflect this
(Reporter)

Comment 2

15 years ago
Created attachment 102270 [details]
output log

Comment 3

15 years ago
Bishakha,

The first failure might be related to a socket error. It would be useful to
rerun this test on a Win2K server machine which lifts limitation on connections.

As far as the second one, too bad Win2K doesn't have core files. Is there a
Drwatson report on the machine ?
(Assignee)

Comment 4

15 years ago
The second failure (Segmentation violation	bltest)
cannot be a bug in NSS 3.6 because the bltest in NSS
3.2.2 (the basis of our backward compatibility testing)
is linked with static NSS libraries.  So the crash of
bltest is either a bug in NSS 3.2.2 or a bug in the new
NSPR 4.2.2.  (bltest is linked with NSPR DLLs.)

Can we reproduce the crash of bltest reliably?

I believe the abort of tstclnt with exit status 134
is bug 86528, which was fixed in NSS 3.3.  tstclnt in
NSS 3.2.2 exits with -2 on the "write to SSL socket failed"
error, and MKS Korn Shell reports "Abort" with exit
status 134 if a process exits with a negative number.
So I think the abort of tstclnt is expected and should
be ignored.  Bishakha, please look at the output.log
files of the test runs that passed and see if they also
contain the same "Abort" messages from tstclnt.
Priority: -- → P1
Target Milestone: --- → 3.6
(Reporter)

Comment 5

15 years ago
| Can we reproduce the crash of bltest reliably?

I don't have rsh installed on Miller, and I don't have access to the lab till
next morning. Meanwhile, I have started the QA on my laptop, which is also a
Win2000 machine.

Julien, I'll be able to check if there is a DrWatson report on the machine
tomorrow morning.

|Bishakha, please look at the output.log
|files of the test runs that passed and see if they also
|contain the same "Abort" messages from tstclnt.

Yes, this is so. The other run on Miller (on the DBG bld) also reports the
following in its output log:
selfserv started at Tue Oct  8 16:56:25 PDT 2002
tstclnt -p 8443 -h MILLER -q -d . <
W:/nss/nss322/builds/20010820.1/blowfish_NT4.0_Win95/mozilla/security/nss/tests/ssl/sslreq.txt

tstclnt -p 8443 -h MILLER -f -d . -w bogus -n TestUser \
        <
W:/nss/nss322/builds/20010820.1/blowfish_NT4.0_Win95/mozilla/security/nss/tests/ssl/sslreq.txt
tstclnt: write to SSL socket failed: SSL peer cannot verify your certificate.
[6] + Done(134) ?
  952	Abort	tstclnt
ssl.sh: WARNING! Testclient returned 134, expect 
             254 (no error as tmp workaround)

So we can ignore this reported error in the log

(Assignee)

Comment 6

15 years ago
I found that the bltest segmentation violation in
the RSA Encrypt and Decrypt tests in backward
compatibility testing of the WIN95 OPT build is a
known problem (bug 82393 and bug 96472), so I am
resolving this as a duplicate.

Sonja, please verify that this is a duplicate.

*** This bug has been marked as a duplicate of 82393 ***
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → DUPLICATE

Comment 7

15 years ago
yes, looks like the same bug to me too. We need to go through the qa scripts and
reduce the environment variables, I'll file a qa bug on this.
You need to log in before you can comment on or make changes to this bug.