Closed
Bug 1872707
Opened 1 year ago
Closed 1 year ago
don't run custom-car toolchain tasks before building latest chromium, reuse tasks which ran for the push
Categories
(Testing :: Raptor, task, P1)
Testing
Raptor
Tracking
(firefox123 fixed)
RESOLVED
FIXED
123 Branch
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: aryx, Assigned: aryx)
References
Details
Attachments
(1 file)
Don't schedule custom-car toolchain tasks when Chromium gets built for its performance testing with browsertime but let the custom-car tasks scheduled for the push get reused.
This will free some scarce older physical macOS hardware machines. The current config blocks builds (profile-guided optimization) from running.
![]() |
Assignee | |
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Severity: -- → S3
Priority: -- → P1
Comment 2•1 year ago
|
||
Bug 1867068 somewhat related for some future improvements
See Also: → 1867068
Pushed by archaeopteryx@coole-files.de:
https://hg.mozilla.org/integration/autoland/rev/7089b8d7fca5
re-use toolchain custom-car tasks when Chromium gets built for its browsertime performance testing. r=kshampur,taskgraph-reviewers,ahal DONTBUILD
Comment 4•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox123:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•