Investigate using bugbug to optimize source-test tasks
Categories
(Firefox Build System :: Task Configuration, task, P3)
Tracking
(Not tracked)
People
(Reporter: ahal, Unassigned)
Details
Currently we only look at the test kind when optimizing things with bugbug. Though there are certain source-test tasks that should likely be optimized in this manner as well. The puppeteer tasks defined here come to mind:
https://searchfox.org/mozilla-central/source/taskcluster/ci/source-test/remote.yml#35
These specific tasks already emit an errorsummary.log, so may be fairly easy to integrate. Most other source-test tasks don't emit an errorsummary (or even use mozlog), so would be harder.
I'm not sure what if anything is needed on the bugbug side to get these tasks selected. On the taskgraph side we'd at least need to assign them an optimizer that uses bugbug.
Comment 1•6 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #0)
I'm not sure what if anything is needed on the
bugbugside to get these tasks selected. On the taskgraph side we'd at least need to assign them an optimizer that usesbugbug.
Right now I'm filtering them out, but adding them should be somewhat trivial (as for builds, we might have to tune it to make it work well, but probably source-tests share enough characteristics with test that no tuning will be required).
Description
•