Update binhost test for Parallel CQ |
|||
Issue descriptionThe binhost test is important. It makes sure that we are generating chrome prebuilts for all builders that require a chrome prebuilt to be able to succeed. If it fails, the build configs in question would fail in production. The parallel CQ will redefine which build configs are "active", which will confuse the binhost test. Solutions: A) Give binhost a robust way to know which configs are active. B) Remove the chrome prebuilt requirement for all builders. B has substantial robustness and performance implications, but makes the PFQ vs other builds (especially edge conditions) much more straight forward.
,
Dec 5
,
Dec 5
From lannm: > I'm not sure that any work is needed for this specifically. I believe we will need to continue generating the in-tree build configs, though the master source of that data will move.
,
Dec 5
Yes, but we generate a lot of configs that don't get actively scheduled, and binhost test does not validate that they can be built. In fact, we know that a bunch of them can't. Another solution is to have binhost test cover every config, scheduled or not. Maybe that's the right approach, but will imply that we add coverage for a lot more boards to the Chrome PFQ to generate the additional prebuilts.
,
Dec 5
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dgarr...@chromium.org
, Dec 5