Closed
Bug 291855
Opened 20 years ago
Closed 19 years ago
SSL tests should not use hardcoded port
Categories
(NSS :: Test, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: julien.pierre, Assigned: jason.m.reid)
Details
Currently, the NSS QA uses the hardcoded port 8443 . This prevents multiple tinderboxes or QA runs from running simultaneously on the same machine. Collisions are a nightly occurrence for the QA at Sun. The QA should be able to use a port dynamically chosen based on something unique to the test environment, such as the PID of the shell process that starts the test.
Comment 1•20 years ago
|
||
8443 is the *default* value of the PORT variable.
In ssl.sh, we have:
PORT=${PORT-8443}
You can specify an alternative port by setting the
PORT environment variable to that port number.
Is this good enough?
Comment 2•20 years ago
|
||
I should add that we were using the PORT environment variable in our Tinderbox scripts. Our QA script mozilla/security/nss/tests/header has a -p option that sets the PORT environment variable.
Updated•20 years ago
|
QA Contact: bishakhabanerjee → jason.m.reid
| Reporter | ||
Comment 3•19 years ago
|
||
Yes, this is good enough. Marking WORKSFORME.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•