Closed
Bug 1708256
Opened 4 years ago
Closed 4 years ago
Stop using the browser-child.js framescript to measure content process startup performance in talos tests
Categories
(Testing :: Talos, task, P1)
Testing
Talos
Tracking
(firefox90 fixed)
RESOLVED
FIXED
90 Branch
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
Details
Attachments
(1 file)
Currently startup performance in talos tests appears to be measured by the loading of the browser-child.js frame script (https://searchfox.org/mozilla-central/rev/3aef835f6cb12e607154d56d68726767172571e4/toolkit/content/browser-child.js#15-19). Once bug 1708254 is fixed, this will become the only purpose of the browser-child.js framescript, and it should be moved to some other mechanism to eliminate the framescript.
|
||
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P3
|
Assignee | |
Comment 1•4 years ago
|
||
|
||
Updated•4 years ago
|
Assignee: nobody → nika
Status: NEW → ASSIGNED
|
|
||
Updated•4 years ago
|
Priority: P3 → P1
|
|
Assignee | |
Comment 2•4 years ago
|
||
The change I made in the attacted patch only removes the browser-child.js frame script, and still continues to use a framescript to measure performance, so correcting the name of the bug. This will need to change eventually.
Summary: Stop using framescripts to measure content process startup performance in talos tests → Stop using the browser-child.js framescript to measure content process startup performance in talos tests
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/26c866675e7a
Remove the browser-child.js frame script, r=mconley,perftest-reviewers
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•