Chromeos config unittest to confirm PFQ builders have paladin equivalents. |
||||||
Issue descriptionIt seems that we need to have a paladin builder equivalent for every PFQ builder (not yet sure why). So... we should have a unittest that confirms we have an active paladin for every active PFQ builder.
,
Apr 14 2017
,
Apr 14 2017
We have such a test: testActivePfqsHavePaladins. However, it was making some now broken assumptions about what it means to have a waterfall set.
,
Apr 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/a53bb43752f2402fdb122b0d5ae2a75789322baf commit a53bb43752f2402fdb122b0d5ae2a75789322baf Author: Don Garrett <dgarrett@google.com> Date: Tue Apr 18 05:50:19 2017 chromeos_config_unittest: Verify PFQ builders are on the CQ. We have long had a unittest to ensure that Chrome PFQ builders are represented in the CQ, but it was broken by changes to our waterfall settings. Rewrite the test to be more robust. Also, add support for the Android PFQ. BUG= chromium:674242 TEST=run_tests Change-Id: Id89f11f288f7bd9638d5c02d08384e29cb87bd29 Reviewed-on: https://chromium-review.googlesource.com/477596 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> [modify] https://crrev.com/a53bb43752f2402fdb122b0d5ae2a75789322baf/cbuildbot/chromeos_config_unittest.py
,
Apr 18 2017
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by autumn@chromium.org
, Jan 3 2017