v8/test/test262/BUILD.gn
machenbach 0d65554c05 [gn] Port test262 archiving to gn
This calls the action that archives test262 in gn. In gn
we can't specify an action output outside the product
directory. This works around it with an extra action
stamp file in the product directory, while the archive
remains in the test directory.

We don't want to generate the archive in the product
directory, as some legacy archiving scripts might include
it and it's too large. It should only be included in the
swarming tasks that are going to use it for testing.

BUG=chromium:474921

Review-Url: https://codereview.chromium.org/2034713005
Cr-Commit-Position: refs/heads/master@{#36731}
2016-06-06 08:56:58 +00:00

35 lines
664 B
Plaintext

# Copyright 2016 the V8 project authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.
import("../../gni/isolate.gni")
if (v8_test_isolation_mode != "noop") {
action("archive_test262") {
visibility = [ ":*" ]
script = "archive.py"
inputs = [
"list.py",
]
sources = exec_script("list.py", [], "list lines")
outputs = [
"$target_gen_dir/test262_archiving.stamp",
]
args = rebase_path(outputs, root_build_dir)
}
}
v8_isolate_run("test262") {
deps = [
":archive_test262",
"../..:d8_run",
]
isolate = "test262.isolate"
}