Closed
Bug 1546471
Opened 5 years ago
Closed 5 years ago
Add a perf-chrome try preset
Categories
(Developer Infrastructure :: Try, enhancement)
Developer Infrastructure
Try
Tracking
(firefox68 fixed)
RESOLVED
FIXED
mozilla68
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: bgrins, Assigned: bgrins)
References
Details
Attachments
(1 file)
When making a change that primarily affects the browser chrome, there are a bunch of perf tests that are unlikely to regress. We should add a preset that includes only the relevant tests.
|
Assignee | |
Comment 1•5 years ago
|
||
This skips a number of talos jobs that are unlikely to be affected
by due a browser-chrome specific change
Run with: ./mach try fuzzy --preset perf-chrome
Pushed by bgrinstead@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4e9444533877 Add a new try preset for talos when making changes to the browser chrome r=mconley
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
|
||
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•