Backward compatibility tests on Linuxes failing on nightly builds of tip



16 years ago
16 years ago


(Reporter: Bishakha Banerjee, Assigned: Bishakha Banerjee)



Firefox Tracking Flags

(Not tracked)




16 years ago
I see from the script that it fails while trying to create CA, while trying to
execute this part of

CU_ACTION="Creating CA Cert DB"
certu -N -d . -f ${R_PWFILE} 2>&1
if [ "$RET" -ne 0 ]; then
    Exit 5 "Fatal - failed to create CA"

The failure in the output file is listed as this (certutil - command not found):

certutil -N -d . -f ../
certutil: command not found Exit: 5 Fatal - failed to create CA

I checked all the paths, they appear OK.  The thing I haven't checked is whether
"" (I assume a temp file with that particular process ID) exists or
not during the execution. The same script works OK on the Solaris and AIX machines.


16 years ago
Priority: -- → P1
Target Milestone: --- → 3.6

Comment 1

16 years ago
We got the builds to work here, Linux 2.4 is building right now, and I'll see if
I can reproduce the behavior with a tip build

Comment 2

16 years ago
Sonja reported that the Linux BC tests on the tip passed yesterday. The scripts
she used the scripts that are checked in to CVS.

So it must be a Netscape specific problem. I "echoed" the paths, SHLIBPATHs and
LD_LIBRARY_PATHS, and they all appear OK. In any case, the same scripts work on
other Unix systems here.

Here's the path info echoed out:
TESTSCRIPTDIR /share/builds/sbsrel2/nss/nsstip/../nss322/builds/20010820.1/y2sun
TESTDIR /share/builds/sbsrel2/nss/nsstip/builds/20020710.1/spd04_Solaris8/mozill
PATH  /share/builds/sbsrel2/nss/nsstip/../nss322/builds/20010820.1/y2sun2_Solari
SHLIBPATH /share/builds/sbsrel2/nss/nsstip/builds/20020710.1/spd04_Solaris8/mozi
LIBPATH /share/builds/sbsrel2/nss/nsstip/builds/20020710.1/spd04_Solaris8/mozill

Next, Sonja gave me some good suggestions. From her email:
which compiler and redhat version (cat /etc/redhat*) are you using on Linux?
There are a lot of incompatibilities, we were using a homegrown gcc 3.0.x for a
while, which will break backward compatibility to 2.96. Also, if the NSS version
that you are running against was built on Linux 2.2 (Redhat 6.x) and the 2.4
directory (redhat 7.x) is just a symlink, it will cause troubles. You might want
to check with Anthony on that.

Since we (NSS lab) did not have a Linux 2.2 machine, I had not been running
nightly QA on it. Hence it was also not obvious here. I used Anthony's Linux 2.2
machine, and BC tests worked. With Anthony's permission, I added "spd09" to the
nightly QA list. It looks like there were probably space issues on sbsrel2
yesterday, some of the builds failed, and some of the nightly QA is reported as
incomplete (the files got created, but nothing written in them). I have also
lost my results from yesterday testing, since Anthony removed all build and QA
tress till yesterday to make space.

However, what I had found is that we are currently building on Red Hat Linux
Advanced Server, and our BC testing is done against either shabadoo_Linux2.2
(for Lin 2.2) and y2sun2_Solaris8 (for Lin 2.4). 
I also tested on "spd16", the machine Anthony uses to build the other Linux
build, and tested against scripts in the y2Sun2_Solaris8 directory. Those tests
failed. Also, the SHLIBPATH and the LIBPATH point to libraries in

Sonja, the build that you tested against, did you build on a Lin 2.4 machine?


Comment 3

16 years ago
This bug is caused by a local configuration problem at Netscape.
Our BC test baseline NSS 3.2.2 build has Linux2.4*.OBJ as symlinks
pointing to nonexistent directories.  We should ask Anthony to
remove those Linux2.4*OBJ symlinks and build
nss/nss322/builds/20010820.1 on Linux 2.4.

Comment 4

16 years ago
Hi Wan-Teh,

I've already asked Anthony to build on a Linux 2.4 machine. He was going to
build with the NSS_3_2_2_RTM tag, which is the same as the 20010820.1 build. He
will be using on one running RedHat 7.1, as that is probably what was there at
the time.


Comment 5

16 years ago

Comment 6

16 years ago
marking fixed
Last Resolved: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.