Scale back the number of raptor-browsertime test jobs running in CI
Categories
(Testing :: Raptor, task, P1)
Tracking
(firefox73 fixed)
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | fixed |
People
(Reporter: rwood, Assigned: rwood)
Details
Attachments
(1 file)
Bug 1590561 landed a refactor to the btime tp6 desktop test INI and taskcluster config, and also we turned on 6 more test pages.
For each page we are running the page-load test with a corresponding visual metrics task. Also I notice there is a conditioned profile job also for each page, and each one of those also has a visual metrics task.
This means there are 64 browsertime tp6 jobs running on EACH platform, x 11 platforms (minimum) = 704 browsertime desktop jobs (all tier 3) minimum per push on mozilla-central [1].
This is way too many. I'm going to remove all the test pages except for one, for a start. We should only roll out all the pages if/when we decide to switch to browsertime for good and at the same time turn off the corresponding tp6 pages on the raptor-webext side, so not to duplicate jobs. Also we shouldn't turn on more pages until the conditioned profiling work is done - we shouldn't run conditioned profile jobs in parallel except on try as that doubles the jobs too.
[1] https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&tier=1%2C2%2C3&searchStr=btime
|
Assignee | |
Comment 1•6 years ago
|
||
|
|
Assignee | |
Comment 2•6 years ago
|
||
|
|
Assignee | |
Comment 3•6 years ago
|
||
Also going to only run on central on *shippable/opt platforms, and removing the fission variant. Can push to try for the others.
|
|
Assignee | |
Comment 4•6 years ago
|
||
|
|
Assignee | |
Comment 5•6 years ago
|
||
|
||
Comment 7•6 years ago
|
||
| bugherder | ||
Description
•