1 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
2 # Use of this source code is governed by a BSD-style license that can be
3 # found in the LICENSE file.
5 # This file is meant to be included into a target to provide a rule
6 # to "build" .isolate files into a .isolated file.
8 # To use this, create a gyp target with the following form:
10 # ['test_isolation_mode != "noop"', {
13 # 'target_name': 'foo_test_run',
19 # '../build/isolate.gypi',
30 # Note: foo_test.isolate is included and a source file. It is an inherent
31 # property of the .isolate format. This permits to define GYP variables but is
32 # a stricter format than GYP so isolate.py can read it.
34 # The generated .isolated file will be:
35 # <(PRODUCT_DIR)/foo_test.isolated
37 # See http://dev.chromium.org/developers/testing/isolated-testing/for-swes
38 # for more information.
42 '../build/util/version.gypi',
46 'rule_name': 'isolate',
47 'extension': 'isolate',
49 # Files that are known to be involved in this step.
50 '<(DEPTH)/tools/isolate_driver.py',
51 '<(DEPTH)/tools/swarming_client/isolate.py',
52 '<(DEPTH)/tools/swarming_client/run_isolated.py',
54 # Disable file tracking by the build driver for now. This means the
55 # project must have the proper build-time dependency for their runtime
56 # dependency. This improves the runtime of the build driver since it
57 # doesn't have to stat() all these files.
59 # More importantly, it means that even if a isolate_dependency_tracked
60 # file is missing, for example if a file was deleted and the .isolate
61 # file was not updated, that won't break the build, especially in the
62 # case where foo_tests_run is not built! This should be reenabled once
63 # the switch-over to running tests on Swarm is completed.
64 #'<@(isolate_dependency_tracked)',
69 '<(DEPTH)/tools/isolate_driver.py',
70 '<(test_isolation_mode)',
71 '--isolated', '<(PRODUCT_DIR)/<(RULE_INPUT_ROOT).isolated',
72 '--isolate', '<(RULE_INPUT_PATH)',
74 # Variables should use the -V FOO=<(FOO) form so frequent values,
75 # like '0' or '1', aren't stripped out by GYP. Run 'isolate.py help' for
78 # This list needs to be kept in sync with the cmd line options
79 # in src/build/android/pylib/gtest/setup.py.
81 # Path variables are used to replace file paths when loading a .isolate
83 '--path-variable', 'DEPTH', '<(DEPTH)',
84 '--path-variable', 'PRODUCT_DIR', '<(PRODUCT_DIR) ',
86 # Extra variables are replaced on the 'command' entry and on paths in
87 # the .isolate file but are not considered relative paths.
88 '--extra-variable', 'version_full=<(version_full)',
90 '--config-variable', 'OS=<(OS)',
91 '--config-variable', 'CONFIGURATION_NAME=<(CONFIGURATION_NAME)',
92 '--config-variable', 'chromeos=<(chromeos)',
93 '--config-variable', 'component=<(component)',
94 '--config-variable', 'fastbuild=<(fastbuild)',
95 # TODO(kbr): move this to chrome_tests.gypi:gles2_conform_tests_run
96 # once support for user-defined config variables is added.
98 'internal_gles2_conform_tests=<(internal_gles2_conform_tests)',
99 '--config-variable', 'icu_use_data_file_flag=<(icu_use_data_file_flag)',
100 '--config-variable', 'libpeer_target_type=<(libpeer_target_type)',
101 '--config-variable', 'use_openssl=<(use_openssl)',
102 '--config-variable', 'target_arch=<(target_arch)',
105 # Note: When gyp merges lists, it appends them to the old value.
107 # <(mac_product_name) can contain a space, so don't use FOO=<(FOO)
110 '--extra-variable', 'mac_product_name', '<(mac_product_name)',
113 ["test_isolation_outdir!=''", {
114 'action': [ '--isolate-server', '<(test_isolation_outdir)' ],
116 ['test_isolation_fail_on_missing == 0', {
117 'action': ['--ignore_broken_items'],
119 ["test_isolation_mode == 'prepare'", {
121 '<(PRODUCT_DIR)/<(RULE_INPUT_ROOT).isolated.gen.json',
125 '<(PRODUCT_DIR)/<(RULE_INPUT_ROOT).isolated',