[wasm] Skip slow test
The test allocates a lot of wasm memories. This got a low slower after https://crrev.com/c/3190476, because we can now allocate more than 102 memories, and do not explicitly trigger a GC any more to get rid of unused memories. We should figure out how to tell the GC about the external memory such that the memories get collected earlier. R=ahaas@chromium.org Bug: v8:12076, v8:12278 Change-Id: I9b8795a9999a806380d86f22e751de2727942648 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3196131 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#77164}
This commit is contained in:
parent
6040caf5da
commit
0cb6323bf1
@ -80,7 +80,6 @@
|
||||
# BUG(v8:9506): slow tests.
|
||||
'wasm/shared-memory-worker-explicit-gc-stress': [PASS, SLOW],
|
||||
'wasm/shared-memory-worker-gc-stress': [PASS, SLOW],
|
||||
'wasm/shared-memory-gc-stress': [PASS, SLOW],
|
||||
|
||||
# https://crbug.com/1129854
|
||||
'tools/log': ['arch == arm or arch == arm64', SKIP],
|
||||
|
@ -34,4 +34,5 @@ function RunSomeAllocs(total, retained, pages, max = pages) {
|
||||
RunSomeAllocs(10, 1, 1, 1);
|
||||
RunSomeAllocs(100, 3, 1, 1);
|
||||
RunSomeAllocs(1000, 10, 1, 1);
|
||||
RunSomeAllocs(10000, 20, 1, 1);
|
||||
// TODO(12278): Make this faster (by collection memories earlier?) and reenable.
|
||||
// RunSomeAllocs(10000, 20, 1, 1);
|
||||
|
Loading…
Reference in New Issue
Block a user