Closed Bug 1478756 Opened Last year Closed Last year

Stop running raptor-chrome tasks on (pgo|opt) and QuantumReference platforms

Categories

(Testing :: Raptor, enhancement)

Version 3
enhancement
Not set

Tracking

(firefox63 fixed)

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: ahal, Assigned: rwood)

Details

Attachments

(1 file)

The chrome binary we use is independent from the buildtype of Firefox we use, so we're essentially running the same chrome task's 3 times per platform. We should only run them on a single build variant (either opt or pgo, whatever is closest to what they actually are).

We might even want to consider creating new "Chromium Linux opt" treeherder platform lines since they aren't related to the Firefox platform whatsoever. Whether it's worth creating a new platform line for a handful of tasks is debatable though.
Yes to both IMO. Great idea: separate line for Chromium - only after fetch tasks are ready so anyone else who sees that and wants to add their own Chromium jobs will be able to get a build from our own CI.
With the patch in comment 2 applied, ./mach try fuzzy (search for raptor chrome) shows that none of the raptor chrome jobs/tasks are on pgo or qr builds anymore.
Comment on attachment 8995589 [details]
Bug 1478756 - Stop running raptor-chrome tasks on (pgo|opt) and QuantumReference platforms;

https://reviewboard.mozilla.org/r/260002/#review267088

Thanks, lgtm! This will conflict with my unity-webgl patch, but go ahead and land it and I'll rebase on top when I get back.
Attachment #8995589 - Flags: review?(ahal) → review+
Assignee: nobody → rwood
Status: NEW → ASSIGNED
Thanks Andrew!
Pushed by rwood@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e09475185677
Stop running raptor-chrome tasks on (pgo|opt) and QuantumReference platforms; r=ahal
https://hg.mozilla.org/mozilla-central/rev/e09475185677
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.