1 # When changing this file, you can (and should) validate your changes by
2 # running |./site_utils/suite_scheduler/suite_scheduler.py --sanity|
4 # When adding tests to a suite, if one (or more) of the tests contains
5 # DEPENDENCIES, then the number of different host specifications required
6 # can increase. This means that the number of physical machines the suite
7 # must ask for increases, as if a suite needs two different machines, and
8 # only asks for one, then there's going to be some set of tests that can't
9 # run. The sanity check will describe to you what suites to set at what
10 # number of machines to make sure all suites can run.
15 [WeeklyKernelRegressions]
17 suite: kernel_weekly_regression
22 [WeeklyPowerRequirements]
24 suite: power_requirements
28 [WeeklyVideoRegressions]
30 suite: video_weekly_regression
43 suite: graphics_per-build
60 [KernelDailyRegression]
62 suite: kernel_daily_regression
67 [KernelDailyBenchmarks]
69 suite: kernel_daily_benchmarks
73 [KernelPerBuildRegression]
75 suite: kernel_per-build_regression
80 [KernelPerBuildBenchmarks]
82 suite: kernel_per-build_benchmarks
102 suite: network3g_tmobile
109 suite: network3g_verizon
114 [Network3g_pseudomodem]
116 suite: network3g_pseudomodem
145 # Not a part of perf build because it requires 3 machines.
232 # run only and post-ALEX platforms (so do not run mario, zgb, and alex)
246 [FirmwarePerBuildRegression_normal]
252 [FirmwarePerBuildRegression_dev]
258 [FirmwarePerBuildRegression_ec]
265 # We need to figure out how we can work out the scheduling of this test.
279 suite: network_nightly