Open
Bug 919315
Opened 11 years ago
Updated 2 years ago
add mochitest server options to CLI options
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: k0scist, Unassigned)
Details
add mochitest server options to CLI options See https://bugzilla.mozilla.org/show_bug.cgi?id=746243#c101 (etc) webServer, httpPort and sslPort are set on the options instance in `mochitest_options`: http://hg.mozilla.org/mozilla-central/file/8b4d14afc4f6/testing/mochitest/mochitest_options.py#l388 They aren't in fact command line options however; they should be! Note that they are already (sorta, remoteWebServer ~ webServer) options for B2GOptions: http://hg.mozilla.org/mozilla-central/file/8b4d14afc4f6/testing/mochitest/mochitest_options.py#l542
Comment 1•11 years ago
|
||
I don't think these ports need to be configurable, necessarily, since we probably have them hardcoded all over the place. The remote harnesses need them configurable, since the server is running on one machine and the tests on another.
Reporter | ||
Comment 2•11 years ago
|
||
I'm not sure if there is a usecase for specifying a non-in-tree server; guessing not, being prohibited by the ability to interpret .sjs files (although probably doable in node). However, I would guess/suppose that if we parallelize mochitest that we will need to/may want to specify the ports. That said, I'm content closing. The way it is now doesn't hurt anything
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•