For autoland, use "opt" builds instead of "shippable" builds
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(Not tracked)
People
(Reporter: Sylvestre, Unassigned)
References
(Blocks 1 open bug)
Details
shippable builds are too long to build and it delays the test process.
Idea from Eric.
|
||
Comment 1•4 years ago
|
||
We are already doing this for try (bug 1638014 and bug 1638945).
|
||
Comment 2•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
Reporter | |
Updated•4 years ago
|
|
|
Reporter | |
Updated•4 years ago
|
|
||
Comment 3•4 years ago
|
||
Instrumented builds are just phase 1 of shippable builds that we use during the "run" phase, we wouldn't want to use those.
|
||
Comment 4•4 years ago
|
||
How are we going to track performance then? All perf tests run on shippable. If we're going to backfill often, then that's not really helping.
|
|
||
Comment 5•4 years ago
|
||
Before reaching to this, we should finish bug 1637544, and improve the build times for the shippable build itself (the new dump_syms will help a lot, and there are other things in the pipe that will improve things too).
|
||
Comment 6•4 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #4)
How are we going to track performance then? All perf tests run on shippable. If we're going to backfill often, then that's not really helping.
We may want to run perf tests against opt on autoland, if we proceed with this bug. If we see a performance regression on central that isn't detected on autoland, then we can backfill shippable.
|
|
Reporter | |
Updated•4 years ago
|
Description
•