Closed
Bug 1486568
Opened 6 years ago
Closed 6 years ago
forceNewProcess reuses the preallocated process
Categories
(Testing :: Mochitest, enhancement)
Tracking
(firefox63 fixed)
RESOLVED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: Felipe, Assigned: Felipe)
References
Details
(Whiteboard: [fxperf:p1])
Attachments
(1 file)
It looks like that the forceNewProcess option from BrowserTestUtils doesn't always _really_ force a new process. Bug 1483444 demonstrated an issue (see comment 6 - 8 there) where forceNewProcess is being used but because of the preloallocated process manager, a process is reused and that is interfering with the test.
|
Assignee | |
Updated•6 years ago
|
Assignee: nobody → felipc
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•6 years ago
|
||
|
||
Comment 2•6 years ago
|
||
Comment on attachment 9005011 [details] Bug 1486568 - forceNewProcess option from BrowserTestUtils should ensure that a cached process is not reused. r=mconley Mike Conley (:mconley) (:⚙️) has approved the revision.
Attachment #9005011 -
Flags: review+
Pushed by felipc@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/6d056cbd3254 forceNewProcess option from BrowserTestUtils should ensure that a cached process is not reused. r=mconley
|
|
Assignee | |
Updated•6 years ago
|
Whiteboard: [fxperf:p1]
|
||
Comment 4•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/6d056cbd3254
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•