Closed Bug 1618622 Opened 5 years ago Closed 5 years ago

Support skip-unless-schedules or seta optimization for builds

Categories

(Firefox Build System :: Task Configuration, enhancement)

enhancement
Not set
normal

Tracking

(firefox75 fixed)

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: bc, Assigned: bc)

References

Details

(Whiteboard: [ci-costs-2020:done] )

Attachments

(1 file)

In bug 1608427 we are trying to use seta to control the generation of fuzzing builds. It appears that we need to also change the build optimization to allow seta optimization. I have a patch which I'll submit to phabricator shortly.

The test optimization strategy in taskcluster/taskgraph/optimization/init.py
is an Either of the skip-unless-schedules and seta strategies. Using this in the
build_attr set_schedules_optimization transform allows us to use seta on builds.

Assignee: nobody → bob
Status: NEW → ASSIGNED

Note that this will only affect fuzzing builds since https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/optimize/seta.py#139 will only allow fuzzing builds to be considered low value.

Attachment #9129570 - Attachment description: Bug 1618622 - Use test optimization strategy in build_attrs, r=dustin. → Bug 1618622 - Use fuzzing-builds optimization strategy in build_attrs for fuzzing builds, r=dustin.
Attachment #9129570 - Attachment description: Bug 1618622 - Use fuzzing-builds optimization strategy in build_attrs for fuzzing builds, r=dustin. → Bug 1618622 - Use fuzzing-builds optimization strategy in build_attrs for fuzzing builds, r=tomprince.
Attachment #9129570 - Attachment description: Bug 1618622 - Use fuzzing-builds optimization strategy in build_attrs for fuzzing builds, r=tomprince. → Bug 1618622 - Use fuzzing-builds optimization strategy fuzzing builds, r=aki.
Pushed by bclary@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/628fd1926eab Use fuzzing-builds optimization strategy fuzzing builds, r=aki.

Did I cause this failure in tg ?

0:34.31 taskcluster/taskgraph/test/test_try_option_syntax.py::TestTryOptionSyntax::test_apostrophe_in_message TEST-UNEXPECTED-FAIL
0:34.32 taskcluster/taskgraph/test/test_try_option_syntax.py::TestTryOptionSyntax::test_b_d TEST-UNEXPECTED-FAIL
0:34.32 taskcluster/taskgraph/test/test_try_option_syntax.py::TestTryOptionSyntax::test_b_do TEST-UNEXPECTED-FAIL
0:34.32 taskcluster/taskgraph/test/test_try_option_syntax.py::TestTryOptionSyntax::test_b_dx TEST-UNEXPECTED-FAIL
0:34.32 taskcluster/taskgraph/test/test_try_option_syntax.py::TestTryOptionSyntax::test_b_o TEST-UNEXPECTED-FAIL
0:34.32 taskcluster/taskgraph/test/test_try_option_syntax.py::TestTryOptionSyntax::test_build_o TEST-UNEXPECTED-FAIL
0:34.33 taskcluster/taskgraph/test/test_try_option_syntax.py::TestTryOptionSyntax::test_unknown_args TEST-UNEXPECTED-FAIL

aki: Is this something I caused?

Flags: needinfo?(aki)

No, that started earlier. :whew:

Flags: needinfo?(aki)
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
Whiteboard: [ci-costs-2020:done]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: