[wasm] Skip another test until we have engine-wide GC
If multiple isolates are involved, we can run OOM when creating many wasm memories, because we only trigger GC in one isolate at a time. TBR=titzer@chromium.org No-Try: true Change-Id: I037b5a13c670c5da2abe54b5045df94637c94f72 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706484 Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#62782}
This commit is contained in:
parent
b226315c7f
commit
9d951e63a6
@ -802,6 +802,7 @@
|
||||
# wasm memories each. Before running OOM on a wasm memory allocation we
|
||||
# trigger a GC, but only in the isolate allocating the new memory.
|
||||
'wasm/module-memory': [SKIP],
|
||||
'wasm/shared-memory-gc-stress': [SKIP],
|
||||
}], # 'isolates'
|
||||
|
||||
##############################################################################
|
||||
|
Loading…
Reference in New Issue
Block a user