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
..
third_party	Revert "[wasm] Re-exported globals preserve their identity"	2020-06-24 22:57:41 +00:00
after.js	[wasm][tests] Sync testharness of wasm-js tests with wpt	2020-06-16 08:17:19 +00:00
BUILD.gn	Reland "[wasm] Add a new wasm-js testsuite to run js-api tests"	2018-10-18 20:18:55 +00:00
OWNERS	Use relative paths to OWNERS files	2019-08-12 13:52:52 +00:00
report.js	[wasm][tests] Sync testharness of wasm-js tests with wpt	2020-06-16 08:17:19 +00:00
testcfg.py	[wasm] Add wasm wpt tests to the V8 tests	2021-09-14 19:10:27 +00:00
testharness-additions.js	[wasm][tests] Sync testharness of wasm-js tests with wpt	2020-06-16 08:17:19 +00:00
tests.tar.gz.sha1	[wasm] Update spec tests	2022-04-26 11:55:12 +00:00
wasm-js.status	[wasm] Re-enable spec test	2022-04-26 13:41:32 +00:00