1 # This example experiment file shows how to invoke sets of tests (a 2 # set is a group of tests that can be invoked by a single alias). 3 # There are currently three sets defined for crosperf_Telemetry: 4 # all_perfv2, all_pagecyclers, and all_toolchain_perf. 5 # 6 # You should replace all the placeholders, marked by angle-brackets, 7 # with the appropriate actual values. 8 9 10 name: telemetry_crosperf_suites_example 11 board: <your-board-goes-here> 12 13 # Note: You can specify multiple remotes, to run your tests in parallel on 14 # multiple machines. e.g. "remote: test-machine-1.com test-machine2.come 15 # test-machine3.com" 16 remote: <your-remote-goes-here> 17 18 # The example below will run all the benchmarks in the perf_v2 suite. 19 # The exact list of benchmarks that will be run can be seen in 20 # crosperf/experiment_factory.py 21 benchmark: all_perfv2 { 22 suite:telemetry_Crosperf 23 iterations: 2 24 } 25 26 # The example below will run all the Telemetry page_cycler benchmarks. 27 # The exact list of benchmarks that will be run can be seen in 28 # crosperf/experiment_factory.py 29 benchmark: all_pagecyclers { 30 suite:telemetry_Crosperf 31 iterations: 1 32 } 33 34 # The example below will run all the Telemetry page_cycler benchmarks. 35 # The exact list of benchmarks that will be run can be seen in 36 # crosperf/experiment_factory.py 37 benchmark: all_toolchain_perf { 38 suite:telemetry_Crosperf 39 iterations: 1 40 } 41 42 # Replace the chromeos image below with the actual path to your test image. 43 test_image_1 { 44 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin 45 } 46 47 # Replace the chromeos image below with the actual path to your second 48 # test image (if desired). 49 new_image { 50 chromeos_image:<path-to-your-other-chroot-goes-here>/src/build/images/<board-goes-here>/latest/chromiumos_test_image.bin 51 } 52 53 54 55
