Closed
Bug 1464510
Opened 6 years ago
Closed 6 years ago
test_ssl_status.js needs to be run sequentially (it uses hardcoded ports)
Categories
(Core :: Security: PSM, enhancement, P1)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
mozilla62
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | fixed |
People
(Reporter: keeler, Assigned: keeler)
References
Details
(Whiteboard: [psm-assigned])
Attachments
(1 file)
Like many PSM xpcshell tests, test_ssl_status.js unfortunately uses hardcoded ports, so it can't be run in parallel with any of these other tests.
|
Assignee | |
Updated•6 years ago
|
Assignee: nobody → dkeeler
Priority: P2 → P1
Whiteboard: [psm-backlog] → [psm-assigned]
| Comment hidden (mozreview-request) |
|
||
Comment 2•6 years ago
|
||
| mozreview-review | ||
Comment on attachment 8980768 [details] bug 1464510 - test_ssl_status.js needs to be run sequentially (it uses hardcoded ports) https://reviewboard.mozilla.org/r/246934/#review254048
Attachment #8980768 -
Flags: review?(mgoodwin) → review+
|
|
Assignee | |
Comment 3•6 years ago
|
||
Thanks!
Pushed by dkeeler@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/855d58016594 test_ssl_status.js needs to be run sequentially (it uses hardcoded ports) r=mgoodwin
|
||
Comment 5•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/855d58016594
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•