AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
65200967b7
v8/tools/testrunner/local/variants.py

38 lines
1.4 KiB
Python
Raw Normal View History

[test] Enable test status filtering by variant This adds the possibility to address test cases in the status file with the variant under which the test is running. This is only allowed in top-level sections. Example: [{ 'test-case': [PASS, SLOW], }] ['variant == foo', { 'test-case': [FAIL], }] The test case "test-case" is marked as slow in all variants. Additionally, in variant foo, it'll be expected to fail. This CL also exemplifies the new feature with test cases running under the ignition_turbofan variant. The corresponding legacy flag is deprecated. BUG=v8:5238 Review-Url: https://codereview.chromium.org/2203013002 Cr-Commit-Position: refs/heads/master@{#38342}
2016-08-04 14:41:09 +00:00
# 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.
# Use this to run several variants of the tests.
ALL_VARIANT_FLAGS = {
"default": [[]],
"stress": [["--stress-opt", "--always-opt"]],
"turbofan": [["--turbo"]],
"turbofan_opt": [["--turbo", "--always-opt"]],
[test] Enable test coverage for noturbo BUG=chromium:682617 R=mstarzinger@chromium.org,bmeurer@chromium.org Change-Id: I1dedc4e2a0cb6e5e42b734c7eb99a40164da4229 Reviewed-on: https://chromium-review.googlesource.com/452498 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#43701}
2017-03-09 13:36:23 +00:00
"noturbofan": [["--no-turbo"]],
"noturbofan_stress": [["--no-turbo", "--stress-opt", "--always-opt"]],
[test] Enable test status filtering by variant This adds the possibility to address test cases in the status file with the variant under which the test is running. This is only allowed in top-level sections. Example: [{ 'test-case': [PASS, SLOW], }] ['variant == foo', { 'test-case': [FAIL], }] The test case "test-case" is marked as slow in all variants. Additionally, in variant foo, it'll be expected to fail. This CL also exemplifies the new feature with test cases running under the ignition_turbofan variant. The corresponding legacy flag is deprecated. BUG=v8:5238 Review-Url: https://codereview.chromium.org/2203013002 Cr-Commit-Position: refs/heads/master@{#38342}
2016-08-04 14:41:09 +00:00
"nocrankshaft": [["--nocrankshaft"]],
"ignition": [["--ignition"]],
"ignition_turbofan": [["--ignition-staging", "--turbo"]],
[wasm] asm.js: Add asm_wasm variant to test asm.js->wasm pipeline. BUG= https://bugs.chromium.org/p/v8/issues/detail?id=4203 BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5406 LOG=N R=mstarzinger@chromium.org,machenbach@chromium.org Review-Url: https://codereview.chromium.org/2309833003 Cr-Commit-Position: refs/heads/master@{#39521}
2016-09-19 23:56:50 +00:00
"asm_wasm": [["--validate-asm"]],
Revert of [wasm] Initial signal handler (patchset #60 id:1170001 of https://codereview.chromium.org/2371833007/ ) Reason for revert: ASAN breakage, such as https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/19111/steps/Check/logs/grow-memory Original issue's description: > [wasm] Initial signal handler > > This is basically the minimum viable signal handler for Wasm bounds checks. > It includes the TLS check and the fine grained instructions checks. These > two checks provide most of the safety for the signal handler. Future CLs will > add code range and data range checks for more robustness. > > The trap handling code and data structures are all in src/trap-handler, with > the code that actually runs in the signal handler confined to > src/trap-handler/signal-handler.cc. > > This changes adds a new V8 API that the embedder should call from a signal > handler that will give V8 the chance to handle the fault first. For hosts that > do not want to implement their own signal handler, we include the option to > install a simple one. This simple handler is also used for the tests. > > When a Wasm module is instantiated, information about each function is passed > to the trap handler, which is used to classify faults. These are removed during > the instance finalizer. > > Several future enhancements are planned before turning this on by default. > Obviously, the additional checks will be added to MaybeHandleFault. We are > also planning to add a two-level CodeObjectData table that is grouped by > isolates to make cleanup easier and also reduce potential for contending on > a single data structure. > > BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277 > > Review-Url: https://codereview.chromium.org/2371833007 > Cr-Original-Commit-Position: refs/heads/master@{#43523} > Committed: https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7d1a7a > Review-Url: https://codereview.chromium.org/2371833007 > Cr-Commit-Position: refs/heads/master@{#43755} > Committed: https://chromium.googlesource.com/v8/v8/+/338622d7cae787a63cece1f2e79a8b030023940b TBR=ahaas@chromium.org,bradnelson@google.com,hpayer@chromium.org,jochen@chromium.org,mark@chromium.org,mseaborn@chromium.org,titzer@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277 Review-Url: https://codereview.chromium.org/2744383002 Cr-Commit-Position: refs/heads/master@{#43757}
2017-03-13 20:03:25 +00:00
"wasm_traps": [["--wasm_guard_pages", "--invoke-weak-callbacks"]],
[test] Enable test status filtering by variant This adds the possibility to address test cases in the status file with the variant under which the test is running. This is only allowed in top-level sections. Example: [{ 'test-case': [PASS, SLOW], }] ['variant == foo', { 'test-case': [FAIL], }] The test case "test-case" is marked as slow in all variants. Additionally, in variant foo, it'll be expected to fail. This CL also exemplifies the new feature with test cases running under the ignition_turbofan variant. The corresponding legacy flag is deprecated. BUG=v8:5238 Review-Url: https://codereview.chromium.org/2203013002 Cr-Commit-Position: refs/heads/master@{#38342}
2016-08-04 14:41:09 +00:00
}
# FAST_VARIANTS implies no --always-opt.
FAST_VARIANT_FLAGS = {
"default": [[]],
"stress": [["--stress-opt"]],
"turbofan": [["--turbo"]],
[test] Enable test coverage for noturbo BUG=chromium:682617 R=mstarzinger@chromium.org,bmeurer@chromium.org Change-Id: I1dedc4e2a0cb6e5e42b734c7eb99a40164da4229 Reviewed-on: https://chromium-review.googlesource.com/452498 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#43701}
2017-03-09 13:36:23 +00:00
"noturbofan": [["--no-turbo"]],
"noturbofan_stress": [["--no-turbo", "--stress-opt"]],
[test] Enable test status filtering by variant This adds the possibility to address test cases in the status file with the variant under which the test is running. This is only allowed in top-level sections. Example: [{ 'test-case': [PASS, SLOW], }] ['variant == foo', { 'test-case': [FAIL], }] The test case "test-case" is marked as slow in all variants. Additionally, in variant foo, it'll be expected to fail. This CL also exemplifies the new feature with test cases running under the ignition_turbofan variant. The corresponding legacy flag is deprecated. BUG=v8:5238 Review-Url: https://codereview.chromium.org/2203013002 Cr-Commit-Position: refs/heads/master@{#38342}
2016-08-04 14:41:09 +00:00
"nocrankshaft": [["--nocrankshaft"]],
"ignition": [["--ignition"]],
"ignition_turbofan": [["--ignition-staging", "--turbo"]],
[wasm] asm.js: Add asm_wasm variant to test asm.js->wasm pipeline. BUG= https://bugs.chromium.org/p/v8/issues/detail?id=4203 BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5406 LOG=N R=mstarzinger@chromium.org,machenbach@chromium.org Review-Url: https://codereview.chromium.org/2309833003 Cr-Commit-Position: refs/heads/master@{#39521}
2016-09-19 23:56:50 +00:00
"asm_wasm": [["--validate-asm"]],
Revert of [wasm] Initial signal handler (patchset #60 id:1170001 of https://codereview.chromium.org/2371833007/ ) Reason for revert: ASAN breakage, such as https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/19111/steps/Check/logs/grow-memory Original issue's description: > [wasm] Initial signal handler > > This is basically the minimum viable signal handler for Wasm bounds checks. > It includes the TLS check and the fine grained instructions checks. These > two checks provide most of the safety for the signal handler. Future CLs will > add code range and data range checks for more robustness. > > The trap handling code and data structures are all in src/trap-handler, with > the code that actually runs in the signal handler confined to > src/trap-handler/signal-handler.cc. > > This changes adds a new V8 API that the embedder should call from a signal > handler that will give V8 the chance to handle the fault first. For hosts that > do not want to implement their own signal handler, we include the option to > install a simple one. This simple handler is also used for the tests. > > When a Wasm module is instantiated, information about each function is passed > to the trap handler, which is used to classify faults. These are removed during > the instance finalizer. > > Several future enhancements are planned before turning this on by default. > Obviously, the additional checks will be added to MaybeHandleFault. We are > also planning to add a two-level CodeObjectData table that is grouped by > isolates to make cleanup easier and also reduce potential for contending on > a single data structure. > > BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277 > > Review-Url: https://codereview.chromium.org/2371833007 > Cr-Original-Commit-Position: refs/heads/master@{#43523} > Committed: https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7d1a7a > Review-Url: https://codereview.chromium.org/2371833007 > Cr-Commit-Position: refs/heads/master@{#43755} > Committed: https://chromium.googlesource.com/v8/v8/+/338622d7cae787a63cece1f2e79a8b030023940b TBR=ahaas@chromium.org,bradnelson@google.com,hpayer@chromium.org,jochen@chromium.org,mark@chromium.org,mseaborn@chromium.org,titzer@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277 Review-Url: https://codereview.chromium.org/2744383002 Cr-Commit-Position: refs/heads/master@{#43757}
2017-03-13 20:03:25 +00:00
"wasm_traps": [["--wasm_guard_pages", "--invoke-weak-callbacks"]],
[test] Enable test status filtering by variant This adds the possibility to address test cases in the status file with the variant under which the test is running. This is only allowed in top-level sections. Example: [{ 'test-case': [PASS, SLOW], }] ['variant == foo', { 'test-case': [FAIL], }] The test case "test-case" is marked as slow in all variants. Additionally, in variant foo, it'll be expected to fail. This CL also exemplifies the new feature with test cases running under the ignition_turbofan variant. The corresponding legacy flag is deprecated. BUG=v8:5238 Review-Url: https://codereview.chromium.org/2203013002 Cr-Commit-Position: refs/heads/master@{#38342}
2016-08-04 14:41:09 +00:00
}
ALL_VARIANTS = set(["default", "stress", "turbofan", "turbofan_opt",
[test] Fix typo in testing variant name This makes it possible to directly request testing noturbofan_stress on the command line. BUG=chromium:682617 TBR=mstarzinger@chromium.org,mvstanton@chromium.org,rmcilroy@chromium.org NOTRY=true Change-Id: I6ba9a022c4ef24fb5abe6878d3f2f972e8461eb8 Reviewed-on: https://chromium-review.googlesource.com/453180 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#43748}
2017-03-13 14:18:42 +00:00
"noturbofan", "noturbofan_stress",
[test] Drop testing ignition_staging Removing it from default variants set which will substantially increase test speed for developers. Pure ignition is intended to be tested only on bots unless opted in. BUG=chromium:682617 R=mstarzinger@chromium.org,mvstanton@chromium.org,rmcilroy@chromium.org Change-Id: I98adb81951a0a2d16f52e6b34b98d3a90e178d8a Reviewed-on: https://chromium-review.googlesource.com/452580 Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#43721}
2017-03-10 10:59:34 +00:00
"nocrankshaft", "ignition",
Remove FLAG_min_preparse_length. It originates from the era where we used to run a separate preparse step before parsing and store the function data. Now the usage of preparser is something completely different, so this flag doesn't make sense any more. In addition, this way we get more test coverage for preparser (for small scripts). BUG= Review-Url: https://codereview.chromium.org/2513563002 Cr-Commit-Position: refs/heads/master@{#41110}
2016-11-18 14:06:25 +00:00
"ignition_turbofan", "asm_wasm", "wasm_traps"])
Reference in New Issue Copy Permalink