1186764 - trychooser thinks graphene and horizon builds are part of -p all

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Mike Hommey [:glandium]]

STR:
- open trychooser
- select "both" build types
- select "all" platforms
- note that computed syntax uses "-p all" and that graphene and horizon jobs are checked.
- push to try with that syntax, graphene and horizon jobs are not started.

The same is true for linux64-mulet, but that's a separate problem, because those run on m-i, so they should be part of -p all.

Comment 1

[Chris Cooper [:coop] (he/him)]

(In reply to Mike Hommey [:glandium] from comment #0)
> STR:
> - open trychooser
> - select "both" build types
> - select "all" platforms
> - note that computed syntax uses "-p all" and that graphene and horizon jobs
> are checked.
> - push to try with that syntax, graphene and horizon jobs are not started.

Graphene and horizon are only enabled on larch, so you'd probably need to be pushing a larch-based tree that included the relevant mozconfigs. Is that what you were doing and it still didn't work, or is your point that we shouldn't be scheduling graphene and horizon builds via "-p all" in the first place?

Comment 2

[Mike Hommey [:glandium]]

My point is that what actually happens and what trychooser says will happen don't match.

Comment 3

[Phil Ringnalda (:philor)]

Attachment: Give Graphene and Horizon the "(not run by default)" text and behavior, since they are "try_by_default": False

He meant this.

Comment 4

[Phil Ringnalda (:philor)]

Comment on attachment 8716756 [details] [diff] [review]
Give Graphene and Horizon the "(not run by default)" text and behavior, since they are "try_by_default": False

https://hg.mozilla.org/build/tools/rev/787ac3797a6f