From 9d951e63a690cb201ab287d05815820d663cba37 Mon Sep 17 00:00:00 2001 From: Clemens Hammacher Date: Wed, 17 Jul 2019 18:36:38 +0200 Subject: [PATCH] [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 Commit-Queue: Clemens Hammacher Cr-Commit-Position: refs/heads/master@{#62782} --- test/mjsunit/mjsunit.status | 1 + 1 file changed, 1 insertion(+) diff --git a/test/mjsunit/mjsunit.status b/test/mjsunit/mjsunit.status index 6889b1a79a..07cfcc86ae 100644 --- a/test/mjsunit/mjsunit.status +++ b/test/mjsunit/mjsunit.status @@ -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' ##############################################################################