[autotest] Add dependencies analysis to |suite_scheduler --sanity|
It's quite easy to accidentally make a suite suddenly unable to properly
run once tests start getting added that have DEPENDENCIES in them. Any
time that the number of different machine configurations exceeds the
number of machines allocated to the suite, some tests will never be able
to get run.
Thankfully, we can do roughly the same analysis statically over the
codebase that dynamic_suites does at runtime so that we can generate
instructions on what suites are currently crippled and provide
instructions on how to fix them.
BUG=chromium-os:35828
TEST=There already existed violating suites
$ ./site_utils/suite_scheduler/suite_scheduler.py --sanity
WARNING:root:Increase KernelDailyRegression to |num: 2|
WARNING:root:Increase NightlyRegression to |num: 2|
$ echo $?
1
Change-Id: I5dc7a4f7a12b0a5877b1d4437d2a7562de2d6dc5
Reviewed-on: https://gerrit.chromium.org/gerrit/40455
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Queue: 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 64cc613..c53938a 100644
--- a/site_utils/suite_scheduler/task.py
+++ b/site_utils/suite_scheduler/task.py
@@ -180,6 +180,11 @@
@property
+ def name(self):
+ return self._name
+
+
+ @property
def suite(self):
return self._suite
@@ -194,6 +199,11 @@
return self._pool
+ @property
+ def num(self):
+ return self._num
+
+
def __str__(self):
return self._str