Closed Bug 588131 Opened 15 years ago Closed 15 years ago

Run Sphinx tests on alternate port

Categories

(addons.mozilla.org Graveyard :: Code Quality, defect)

Product:
addons.mozilla.org Graveyard
Component:
Code Quality
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: davedash, Assigned: davedash)

Details

(Whiteboard: [qa-])

Copy those guys at Firefox input and run our sphinx tests on a different port than that of production. This should in theory fix our crazy "too many sphinxes" issue on Hudson.
(In reply to comment #0) > Copy those guys at Firefox input and run our sphinx tests on a different port > than that of production. That will be nice for not killing the hudson my website is talking to. > This should in theory fix our crazy "too many sphinxes" issue on Hudson. Not if preview and next are talking to the same alternate port.
correct - in Input there's a TEST_SPHINX_PORT in settings.py
Great.
http://github.com/jbalogh/zamboni/commit/91e803e5f64833138ad15bb8318415a297a20f29 To resolve the alternate port issue in hudson, the alternate port is based on the executor number.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
Target Milestone: --- → 5.12
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.