Bug 1450392 [wpt PR 8927] - Delete wasm/many-memories.window.js WPT test, a=testonly
authorEric Holk <eholk@chromium.org>
Mon, 09 Apr 2018 21:25:38 +0000
changeset 467237 0f45dceb7d6537805511af50be8820860f44d640
parent 467236 5cbc82f2f03c60af195ae009be4dafd196a2f4ed
child 467238 03fe1ceeb6da887b4d8e2b18e8defafdb51b8d97
push id9165
push userasasaki@mozilla.com
push dateThu, 26 Apr 2018 21:04:54 +0000
treeherdermozilla-beta@064c3804de2e [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1450392, 851081, 547333
milestone61.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1450392 [wpt PR 8927] - Delete wasm/many-memories.window.js WPT test, a=testonly Automatic update from web-platform-testsDelete wasm/many-memories.window.js WPT test Testing for a specific number is causing problems and determining the right number is problematic in general, as running out of memory is always a legitimate possiblity. See https://github.com/WebAssembly/design/issues/1167 for more discussion. In light of this, it's best to just remove the test. Bug: Change-Id: I66e248c8ab851bca0c54fa6fe13b6e93e55f1264 Reviewed-on: https://chromium-review.googlesource.com/851081 Commit-Queue: Brad Nelson <bradnelson@chromium.org> Reviewed-by: Brad Nelson <bradnelson@chromium.org> Cr-Commit-Position: refs/heads/master@{#547333} wpt-commits: fc33be9acfbf8e883fd9683c527aab22d842542b wpt-pr: 8927 wpt-commits: fc33be9acfbf8e883fd9683c527aab22d842542b wpt-pr: 8927
testing/web-platform/meta/MANIFEST.json
testing/web-platform/tests/wasm/many-memories.window.js
--- a/testing/web-platform/meta/MANIFEST.json
+++ b/testing/web-platform/meta/MANIFEST.json
@@ -365212,22 +365212,16 @@
     ]
    ],
    "wasm/create_multiple_memory.worker.js": [
     [
      "/wasm/create_multiple_memory.worker.html",
      {}
     ]
    ],
-   "wasm/many-memories.window.js": [
-    [
-     "/wasm/many-memories.window.html",
-     {}
-    ]
-   ],
    "wasm/wasm_indexeddb_test.https.html": [
     [
      "/wasm/wasm_indexeddb_test.https.html",
      {}
     ]
    ],
    "wasm/wasm_local_iframe_test.html": [
     [
@@ -602401,20 +602395,16 @@
   "wasm/create_multiple_memory.worker.js": [
    "893d408fc56d030416a3c89ae3680dc028ecf1d7",
    "testharness"
   ],
   "wasm/incrementer.wasm": [
    "acdf9d22c042ea3b2637c14b1576b4c8ffb4e97a",
    "support"
   ],
-  "wasm/many-memories.window.js": [
-   "84e98a89e653c39dab16e096286457268dccd195",
-   "testharness"
-  ],
   "wasm/resources/blank.html": [
    "0ddb4f1cf84729ed673295719ec58a3e5d600a12",
    "support"
   ],
   "wasm/resources/frame.html": [
    "1fd433c40c7364f6cc396c2a4a02ad5ee9d6cc49",
    "support"
   ],
deleted file mode 100644
--- a/testing/web-platform/tests/wasm/many-memories.window.js
+++ /dev/null
@@ -1,19 +0,0 @@
-// Copyright 2017 The Chromium Authors. All rights reserved.
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-
-// This test makes sure browsers behave reasonably when asked to allocate a
-// larger number of WebAssembly.Memory objects at once.
-test(function() {
-  let memories = [];
-  try {
-    for (let i = 0; i < 20; i++) {
-      memories.push(new WebAssembly.Memory({initial: 1}));
-    }
-  } catch (e) {
-    if (e instanceof RangeError) {
-      return;
-    }
-    throw e;
-  }
-}, "WebAssembly#CreateManyMemories");