Closed Bug 746147 Opened 12 years ago Closed 12 years ago

Fix TestRun class for dynamic jsbridge port

Categories

(Mozilla QA Graveyard :: Mozmill Automation, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

As seen there seems to be a problem with the dynamic JSBridge port selection (mozmill 1.5.10) at least in the functional testrun for restart tests. Running a restart testrun after a normal testrun causes an out of sync situation:

*** Updating to branch 'default'
pulling from http://hg.mozilla.org/qa/mozmill-tests
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
jsbridge: Server started on port 65447
[...]
INFO Passed: 212
INFO Failed: 1
INFO Skipped: 27
jsbridge: Server started on port 65447
Sorry, cannot connect to jsbridge extension, port 49544

So the port used for the normal tests is getting used again on the extension side for the restart tests. Instead the new port should be used.
Blocks: 686320
So this was not a fault in our testrun class but a silly left-over in the __init__ method of mozrunner itself. We never experienced it before until now. A patch will be attached over on bug 686320.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.