If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

SSL tests should not use hardcoded port

RESOLVED WORKSFORME

Status

NSS
Test
RESOLVED WORKSFORME
13 years ago
12 years ago

People

(Reporter: Julien Pierre, Assigned: Jason Reid)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
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

13 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

13 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.
QA Contact: bishakhabanerjee → jason.m.reid
(Reporter)

Comment 3

12 years ago
Yes, this is good enough. Marking WORKSFORME.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.