suite-scheduler: Get build from wider time range for multi-DUTs
For non tot branch there could be only 1 build per day, so one
failed build can cause us failed to locate most recent build
for a secondary board, and result in skip build for primary
board.
BUG=None
TEST=bin/run_tests
Change-Id: I9aad2c13e78e998c13a1cf73fb60cbe482b9e14c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/suite_scheduler/+/3123969
Commit-Queue: Xianuo Wang <xianuowang@chromium.org>
Tested-by: Xianuo Wang <xianuowang@chromium.org>
Reviewed-by: Sean McAllister <smcallis@google.com>
diff --git a/trigger_receiver.py b/trigger_receiver.py
index eef76f2..56e908e 100644
--- a/trigger_receiver.py
+++ b/trigger_receiver.py
@@ -98,9 +98,12 @@
cros_builds_tuple = event.get_cros_builds(
self._lab_config, self._build_client)
logging.debug('Found CrOS builds: %r', cros_builds_tuple)
- daily_cros_builds_tuple = event.get_daily_cros_builds(
- self._lab_config, self._build_client)
- logging.debug('Found daily CrOS builds: %r', daily_cros_builds_tuple)
+ # Set delta to 3 days here as we only build once per day for non tot
+ # builds, so a single failure on secondary boards may cause a skip
+ # of primary board.
+ recent_cros_builds_tuple = event.get_recent_cros_builds(
+ self._lab_config, self._build_client, delta_days=3)
+ logging.debug('Found recent CrOS builds: %r', recent_cros_builds_tuple)
launch_control_builds = event.get_launch_control_builds(
self._lab_config, self._android_client)
logging.debug('Found launch_control_builds: %r', launch_control_builds)
@@ -114,5 +117,5 @@
cros_builds_tuple=cros_builds_tuple,
firmware_builds=firmware_builds,
configs=config_reader.Configs(lab_config=self._lab_config),
- daily_cros_builds_tuple=daily_cros_builds_tuple)
+ recent_cros_builds_tuple=recent_cros_builds_tuple)
logging.info('Finished processing all tasks')