Closed
Bug 1901813
Opened 1 year ago
Closed 1 year ago
Add chrome-m background resource test
Categories
(Testing :: mozperftest, task, P2)
Testing
mozperftest
Tracking
(firefox130 fixed)
RESOLVED
FIXED
130 Branch
| Tracking | Status | |
|---|---|---|
| firefox130 | --- | fixed |
People
(Reporter: kshampur, Assigned: sparky)
References
Details
(Whiteboard: [fxp][operational])
Attachments
(1 file)
Also maybe rename the task from background-cpu to background-resource ? (since memory is also gathered)
|
Reporter | |
Updated•1 year ago
|
Whiteboard: [fxp]
|
||
Updated•1 year ago
|
|
Assignee | |
Comment 1•1 year ago
|
||
This patch adds a new background resource test for chrome release. The existing background resource test is modified to handle the chrome binary instead of building a separate test for it.
Depends on D217097
|
||
Updated•1 year ago
|
Assignee: nobody → gmierz2
Status: NEW → ASSIGNED
|
|
Reporter | |
Updated•1 year ago
|
Priority: P2 → P1
Pushed by gmierz2@outlook.com:
https://hg.mozilla.org/integration/autoland/rev/8273f41745f0
Add chrome release background resource test. r=perftest-reviewers,kshampur
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox130:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
|
||
Updated•1 month ago
|
Priority: P1 → P2
|
|
||
Updated•1 month ago
|
Whiteboard: [fxp] → [fxp][operational]
|
|
||
Updated•1 month ago
|
Severity: S3 → S2
You need to log in
before you can comment on or make changes to this bug.
Description
•