[autotest] Schedule tests against lumpy-pgo-release builds.
We currently see lumpy-pgo-release builds, and then schedule tests
against lumpy-release. This CL changes the parsing so that we see
pgo-release as a build config type, and then schedule tests against
lumpy-pgo-release as one would expect.
Note that it took a local modification to base_event.ParseBuildName in
order for a local run of suite_scheduler to work. This will get fixed
once a standardized fully parseable naming convention is agreed upon.
BUG=chromium-os:39283
TEST=unit
forced event locally and watched lumpy-pgo-release get scheduled
Change-Id: Ic9dba31e58d342b593a7d84f605bddfb77a81d9c
Reviewed-on: https://gerrit.chromium.org/gerrit/44366
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
diff --git a/site_utils/suite_scheduler/driver.py b/site_utils/suite_scheduler/driver.py
index a28ca4f..aa813b7 100644
--- a/site_utils/suite_scheduler/driver.py
+++ b/site_utils/suite_scheduler/driver.py
@@ -154,7 +154,7 @@
"""
board, type, milestone, manifest = base_event.ParseBuildName(build_name)
branch_builds = {task.PickBranchName(type, milestone): [build_name]}
- logging.info('Testing build %s-%s on %s', milestone, manifest, board)
+ logging.info('Testing build R%s-%s on %s', milestone, manifest, board)
for e in self._events.itervalues():
if e.keyword in keywords: