diff options
Diffstat (limited to 'crosperf/experiment_files/telemetry-crosperf-suites.exp')
-rw-r--r-- | crosperf/experiment_files/telemetry-crosperf-suites.exp | 45 |
1 files changed, 26 insertions, 19 deletions
diff --git a/crosperf/experiment_files/telemetry-crosperf-suites.exp b/crosperf/experiment_files/telemetry-crosperf-suites.exp index cb1a258a..2caa588d 100644 --- a/crosperf/experiment_files/telemetry-crosperf-suites.exp +++ b/crosperf/experiment_files/telemetry-crosperf-suites.exp @@ -1,15 +1,19 @@ -# This is an example experiment file for Crosperf, showing how to run -# a Telemetry test, using test_that and autotest. This is similar to -# the basic_telemetry_crosperf_example (in telemetry-crosperf.exp), -# except that it shows how to invoke suites of tests. There are -# currently two suites defined for crosperf_Telemetry: all_perfv2 and -# all_pagecyclers. +# This example experiment file shows how to invoke sets of tests (a +# set is a group of tests that can be invoked by a single alias). +# There are currently three sets defined for crosperf_Telemetry: +# all_perfv2, all_pagecyclers, and all_toolchain_perf. +# +# You should replace all the placeholders, marked by angle-brackets, +# with the appropriate actual values. + name: telemetry_crosperf_suites_example -# Replace board and remote values below appropriately. e.g. "lumpy" and -# "123.45.678.901" or "my-machine.blah.com". board: <your-board-goes-here> -remote: <your-remote-ip-address-here> + +# Note: You can specify multiple remotes, to run your tests in parallel on +# multiple machines. e.g. "remote: test-machine-1.com test-machine2.come +# test-machine3.com" +remote: <your-remote-goes-here> # The example below will run all the benchmarks in the perf_v2 suite. # The exact list of benchmarks that will be run can be seen in @@ -27,18 +31,21 @@ benchmark: all_pagecyclers { iterations: 1 } -# Replace <path-to-your-chroot-goes-here> and <board-goes-here> below. -# You can optionally add "chrome_src:" followed by the path to a Chrome -# source tree outside your chroot that you wish to use for running -# Telemetry. -old_image { - chromeos_image:<path-to-your-chroot-goes-here>/src/build/images/<board-goes-here>/latest/chromiumos_test_image.bin +# The example below will run all the Telemetry page_cycler benchmarks. +# The exact list of benchmarks that will be run can be seen in +# crosperf/experiment_factory.py +benchmark: all_toolchain_perf { + suite:telemetry_Crosperf + iterations: 1 +} + +# Replace the chromeos image below with the actual path to your test image. +test_image_1 { + chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin } -# Replace <path-to-your-other-chroot-goes-here> and <board-goes-here> below. -# You can optionally add "chrome_src:" followed by the path to a Chrome -# source tree outside your chroot that you wish to use for running -# Telemetry. +# Replace the chromeos image below with the actual path to your second +# test image (if desired). new_image { chromeos_image:<path-to-your-other-chroot-goes-here>/src/build/images/<board-goes-here>/latest/chromiumos_test_image.bin } |