Bug 1622101 [wpt PR 22227] - Restore 'timeout: long' for measure memory tests in WPT, a=testonly
authorUlan Degenbaev <ulan@chromium.org>
Sat, 14 Mar 2020 11:28:49 +0000
changeset 518844 c70afeda1b03d7c4642afb4fbdbb717426ff753b
parent 518843 849a61e2a088e37fb5b84e8f641bfca5389ab02e
child 518845 c3cbc7e54ed417161a92817330b940e266fc4aaf
push id37217
push userccoroiu@mozilla.com
push dateSun, 15 Mar 2020 21:37:59 +0000
treeherdermozilla-central@f9fc9427476e [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1622101, 22227, 1049093, 2101010, 749902
milestone76.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 1622101 [wpt PR 22227] - Restore 'timeout: long' for measure memory tests in WPT, a=testonly Automatic update from web-platform-tests Restore 'timeout: long' for measure memory tests in WPT The annotation is required because the tests run close to 10s timeout in upstream. Bug: 1049093 Change-Id: Ie84bbb389e444c399c13cd9f5983ac1517ed3cee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101010 Auto-Submit: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Robert Ma <robertma@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#749902} -- wpt-commits: 17511ee9281cdd3d7034e60506d1ea7a47b07946 wpt-pr: 22227
testing/web-platform/tests/measure-memory/measure-memory-cross-origin-iframe.tentative.window.js
testing/web-platform/tests/measure-memory/measure-memory-cross-origin-redirecting-iframe.tentative.window.js
testing/web-platform/tests/measure-memory/measure-memory-same-origin-iframe.tentative.window.js
--- a/testing/web-platform/tests/measure-memory/measure-memory-cross-origin-iframe.tentative.window.js
+++ b/testing/web-platform/tests/measure-memory/measure-memory-cross-origin-iframe.tentative.window.js
@@ -1,10 +1,11 @@
 // META: script=/common/get-host-info.sub.js
 // META: script=./resources/common.js
+// META: timeout=long
 'use strict';
 
 promise_test(async testCase => {
   const grandchildLoaded = new Promise(resolve => {
     window.onmessage = function(message) {
       if (message.data === 'grandchild-loaded') {
         resolve(message);
       }
--- a/testing/web-platform/tests/measure-memory/measure-memory-cross-origin-redirecting-iframe.tentative.window.js
+++ b/testing/web-platform/tests/measure-memory/measure-memory-cross-origin-redirecting-iframe.tentative.window.js
@@ -1,10 +1,11 @@
 // META: script=/common/get-host-info.sub.js
 // META: script=./resources/common.js
+// META: timeout=long
 'use strict';
 
 promise_test(async testCase => {
   const grandchildLoaded = new Promise(resolve => {
     window.onmessage = function(message) {
       if (message.data === 'grandchild-loaded') {
         resolve(message);
       }
--- a/testing/web-platform/tests/measure-memory/measure-memory-same-origin-iframe.tentative.window.js
+++ b/testing/web-platform/tests/measure-memory/measure-memory-same-origin-iframe.tentative.window.js
@@ -1,10 +1,11 @@
 // META: script=/common/get-host-info.sub.js
 // META: script=./resources/common.js
+// META: timeout=long
 'use strict';
 
 promise_test(async testCase => {
   const grandchildLoaded = new Promise(resolve => {
     window.onmessage = function(message) {
       if (message.data === 'grandchild-loaded') {
         resolve(message);
       }