[autotest] Admit that suite_scheduler can't always parse everything.
Esoteric builds have been causing us problems, first |pgo-release|, now
|depthcharge-firmware|. Rather than trying to intelligently understand
how to parse these names and schedule against them, even though no one
is even trying to run out-of-line suites against them, let's just
acknowledge the builds that we can't parse, log it so that it's obvious
what's going on, and continue on.
BUG=chromium:218079, chromium-os:39283
TEST=unit, forced a lumpy-release run
Change-Id: I49de7029893bcea2047fecb09ea33835a7168aaa
Reviewed-on: https://gerrit.chromium.org/gerrit/45763
Commit-Queue: Alex Miller <milleral@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
diff --git a/site_utils/suite_scheduler/task.py b/site_utils/suite_scheduler/task.py
index b2bd597..ae2de38 100644
--- a/site_utils/suite_scheduler/task.py
+++ b/site_utils/suite_scheduler/task.py
@@ -14,7 +14,7 @@
pass
-BARE_BRANCHES = ['factory', 'firmware', 'pgo-release', 'depthcharge-firmware']
+BARE_BRANCHES = ['factory', 'firmware']
def PickBranchName(type, milestone):