v8/test/wasm-js/wasm-js.status
Andreas Haas 5cd1a4cf1f [wasm] Re-enable spec test
I cannot reproduce the original problem anymore. The test passes
nicely. If the test (wasm-js/limits) fails again, then we should
just disable it for those platforms where it is failing.

Fixed: v8:11577
Change-Id: I186da2ec2dd8fd518ce4034e8e3838376fefbc3b
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3605814
Reviewed-by: Clemens Backes <clemensb@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/main@{#80186}
2022-04-26 13:41:32 +00:00

69 lines
2.6 KiB
Plaintext

# Copyright 2018 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.
[
[ALWAYS, {
# This test can only be executed in the browser
'wpt/idlharness': [SKIP],
# Failing WPT tests
'wpt/exception/getArg.tentative': [FAIL],
'wpt/exception/toString.tentative': [FAIL],
'wpt/exception/type.tentative': [FAIL],
'wpt/function/constructor.tentative': [FAIL],
'wpt/function/table.tentative': [FAIL],
'wpt/function/type.tentative': [FAIL],
'wpt/global/type.tentative': [FAIL],
'wpt/table/type.tentative': [FAIL],
# Outdated proposal tests.
'proposals/js-types/table/get-set': [FAIL],
'proposals/memory64/table/get-set': [FAIL],
'proposals/simd/table/get-set': [FAIL],
'proposals/tail-call/table/get-set': [FAIL],
'proposals/js-types/memory/constructor': [FAIL],
'proposals/memory64/memory/constructor': [FAIL],
'proposals/simd/memory/constructor': [FAIL],
'proposals/tail-call/memory/constructor': [FAIL],
'proposals/js-types/interface': [FAIL],
'proposals/memory64/interface': [FAIL],
'proposals/simd/interface': [FAIL],
'proposals/tail-call/interface': [FAIL],
# TODO(v8:10556): Remove sub-typing in the reference-types implementation
'proposals/js-types/constructor/instantiate': [FAIL],
'proposals/js-types/global/value-get-set': [FAIL],
'proposals/js-types/instance/constructor': [FAIL],
# These are slow, and not useful to run for the proposals:
'proposals/js-types/limits': [SKIP],
'proposals/simd/limits': [SKIP],
'proposals/memory64/limits': [SKIP],
}], # ALWAYS
['arch == s390 or arch == s390x or system == aix', {
# https://bugs.chromium.org/p/v8/issues/detail?id=8402
'instance/constructor': [SKIP],
'constructor/instantiate': [SKIP],
}], # 'arch == s390 or arch == s390x or system == aix'
['mode == debug or simulator_run or variant != default or arch == arm or tsan or msan or asan', {
# Slow, and we always have the same limits anyway.
# ODroid bots don't have enough memory to run the test.
'limits': [SKIP],
}], # mode == debug or simulator_run or variant != default or arch == arm or tsan or msan or asan
##############################################################################
# TODO(v8:7777): Change this once wasm is supported in jitless mode.
['not has_webassembly or variant == jitless', {
'*': [SKIP],
}], # not has_webassembly or variant == jitless
################################################################################
['variant == stress_snapshot', {
'*': [SKIP], # only relevant for mjsunit tests.
}],
]