HomeSort by relevance Sort by last modified time
    Searched refs:your (Results 1 - 25 of 987) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /external/toolchain-utils/crosperf/experiment_files/
aes_perf.exp 8 board: <your-board-goes-here>
10 # Note: You can specify multiple remotes, to run your tests in parallel on
13 remote: <your-remote-goes-here>
18 # Replace the chromeos image below with the actual path to your test image.
20 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
bloat_perf.exp 8 board: <your-board-goes-here>
10 # Note: You can specify multiple remotes, to run your tests in parallel on
13 remote: <your-remote-goes-here>
22 # Replace the chromeos image below with the actual path to your test image.
24 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
morejs_perf.exp 8 board: <your-board-goes-here>
10 # Note: You can specify multiple remotes, to run your tests in parallel on
13 remote: <your-remote-goes-here>
22 # Replace the chromeos image below with the actual path to your test image.
24 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
non-telemetry-tests.exp 8 board: <your-board-goes-here>
10 # Note: You can specify multiple remotes, to run your tests in parallel on
13 remote: <your-remote-goes-here>
28 # Replace the chromeos image below with the actual path to your test image.
30 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
page_cycler.exp 8 board: <your-board-goes-here>
10 # Note: You can specify multiple remotes, to run your tests in
14 remote: <your-remote-goes-here>
24 # Replace the chromeos image below with the actual path to your test
27 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
telemetry-crosperf-with-external-chrome-src.exp 11 board: <your-board-goes-here>
13 # Note: You can specify multiple remotes, to run your tests in parallel on
16 remote: <your-remote-goes-here>
23 # Replace the chromeos image below with the actual path to your test imnage.
25 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
27 # top of your Chrome source tree. From that directory
telemetry-crosperf-with-profiler.exp 10 board: <your-board-goes-here>
12 # Note: You can specify multiple remotes, to run your tests in parallel on
15 remote: <your-remote-goes-here>
31 # Replace the chromeos image below with the actual path to your test imnage.
33 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
telemetry-without-autotest.exp 10 board: <your-board-goes-here>
12 # Note: You can specify multiple remotes, to run your tests in parallel on
15 remote: <your-remote-goes-here>
19 # (in the test_args field) with the appropriate page set for your test.
21 # Make sure your suite is 'telemtry', NOT 'telemetry_Crosperf'.
28 # Replace the chromeos image below with the actual path to your test image.
30 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
trybot-image.exp 9 board: <your-board-goes-here>
11 # Note: You can specify multiple remotes, to run your tests in parallel on
14 remote: <your-remote-goes-here>
23 # Replace <path-to-your-chroot-goes-here> with the actual directory path
24 # to the top of your ChromimumOS chroot.
26 chromeos_root:<path-to-your-chroot-goes-here>
official-image.exp 9 board: <your-board-goes-here>
11 # Note: You can specify multiple remotes, to run your tests in parallel on
14 remote: <your-remote-goes-here>
22 # Replace <path-to-your-chroot-goes-here> with the actual directory path
23 # to the top of your ChromimumOS chroot.
25 chromeos_root:<path-to-your-chroot-goes-here>
34 # Replace <path-to-your-chroot-goes-here> with actual path.
35 chromeos_root:<path-to-your-chroot-goes-here>
telemetry-crosperf-suites.exp 11 board: <your-board-goes-here>
13 # Note: You can specify multiple remotes, to run your tests in parallel on
16 remote: <your-remote-goes-here>
42 # Replace the chromeos image below with the actual path to your test image.
44 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
47 # Replace the chromeos image below with the actual path to your second
50 chromeos_image:<path-to-your-other-chroot-goes-here>/src/build/images/<board-goes-here>/latest/chromiumos_test_image.bin
telemetry-crosperf.exp 9 board: <your-board-goes-here>
11 # Note: You can specify multiple remotes, to run your tests in parallel on
14 remote: <your-remote-goes-here>
24 # Replace <path-to-your-chroot-goes-here> and <board-goes-here> below.
26 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/vanilla-image/chromiumos_test_image.bin
29 # Replace the chromeos image below with the actual path to your test image.
31 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
page_cycler_perf.exp 8 board: <your-board-goes-here>
10 # Note: You can specify multiple remotes, to run your tests in parallel on
13 remote: <your-remote-goes-here>
42 # Replace the chromeos image below with the actual path to your test image.
44 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
  /frameworks/opt/setupwizard/library/
common-platform-deprecated.mk 3 # Include this make file to build your application against this module.
5 # Make sure to include it after you've set all your desired LOCAL variables.
6 # Note that you must explicitly set your LOCAL_RESOURCE_DIR before including this file.
  /external/llvm/lib/Support/
Atomic.cpp 38 # error No memory fence implementation for your platform!
56 # error No compare-and-swap implementation for your platform!
  /external/swiftshader/third_party/llvm-subzero/lib/Support/
Atomic.cpp 40 # error No memory fence implementation for your platform!
58 # error No compare-and-swap implementation for your platform!
  /test/vti/test_serving/gae/testing/
README.md 7 export GAE_PROJECT=your-project-id
  /device/linaro/bootloader/edk2/
edksetup.sh 19 # CYGWIN users: Your path and filename related environment variables should be
59 echo Run this script from the base of your tree. For example:
70 echo BaseTools not found in your tree, and EDK_TOOLS_PATH is not set.
106 echo BaseTools not found in your tree, and EDK_TOOLS_PATH is not set.
108 echo in your shell, or point EDK_TOOLS_PATH at the directory that contains
  /prebuilts/clang/host/darwin-x86/clang-4393122/share/clang/
clang-rename.py 6 * clang-rename is in your PATH
10 To install, simply put this into your ~/.vimrc
34 Is your file empty?'''
  /prebuilts/clang/host/darwin-x86/clang-4479392/share/clang/
clang-rename.py 6 * clang-rename is in your PATH
10 To install, simply put this into your ~/.vimrc
34 Is your file empty?'''
  /prebuilts/clang/host/darwin-x86/clang-4579689/share/clang/
clang-rename.py 6 * clang-rename is in your PATH
10 To install, simply put this into your ~/.vimrc
34 Is your file empty?'''
  /prebuilts/clang/host/darwin-x86/clang-4630689/share/clang/
clang-rename.py 6 * clang-rename is in your PATH
10 To install, simply put this into your ~/.vimrc
34 Is your file empty?'''
  /prebuilts/clang/host/darwin-x86/clang-4639204/share/clang/
clang-rename.py 6 * clang-rename is in your PATH
10 To install, simply put this into your ~/.vimrc
34 Is your file empty?'''
  /prebuilts/clang/host/darwin-x86/clang-4691093/share/clang/
clang-rename.py 6 * clang-rename is in your PATH
10 To install, simply put this into your ~/.vimrc
34 Is your file empty?'''
  /prebuilts/clang/host/linux-x86/clang-4393122/share/clang/
clang-rename.py 6 * clang-rename is in your PATH
10 To install, simply put this into your ~/.vimrc
34 Is your file empty?'''

Completed in 514 milliseconds

1 2 3 4 5 6 7 8 91011>>