Closed Bug 1334821 Opened 5 years ago Closed 5 years ago
Taskcluster's try syntax should default to -t none
When we started using try_option_syntax, I didn't worry too much about the wrongness of the const/default in https://hg.mozilla.org/mozilla-central/annotate/045d8fe30f546ab08466c9586ce298e6459c2069/taskcluster/taskgraph/try_option_syntax.py#l230 since TC didn't actually do any talos, but now TC does talos, and people do use the fact that buildbot's default for omitting -t is none, and the way we're running unwanted linux64 talos on try is contributing to the way that we have a 12 hour backlog of linux64 talos jobs every weekday.
Probably the right choice here is that the in-tree taskgraph code should delete all talos tasks using a transform, until we're ready to turn them on (those who wish to experiment in try can remove the transform in their try push)
Assignee: nobody → dustin
Component: General → Task Configuration
Comment on attachment 8831458 [details] Bug 1334821: default to `-t none`; https://reviewboard.mozilla.org/r/108012/#review109150
Attachment #8831458 - Flags: review?(philringnalda) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/6e4f767bfa02 default to `-t none`; r=philor
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.