Bug 1468348 [wpt PR 11477] - Fix test flakiness around multi-threaded blob URL revocation., a=testonly
authorMarijn Kruisselbrink <mek@chromium.org>
Fri, 06 Jul 2018 15:31:05 +0000
changeset 425834 cb900853bddcf6a41974f6f9a43805d4a2051631
parent 425833 370f0f30b5640def6b803412306cb23d18522986
child 425835 ed85f95158ecefe5509bed3e181b76da708230d4
push id34267
push userrgurzau@mozilla.com
push dateWed, 11 Jul 2018 22:05:21 +0000
treeherdermozilla-central@3aca103e4915 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1468348, 11477, 851942, 1097230, 566460
milestone63.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 1468348 [wpt PR 11477] - Fix test flakiness around multi-threaded blob URL revocation., a=testonly Automatic update from web-platform-testsFix test flakiness around multi-threaded blob URL revocation. Registering a new blob URL in the worker will ensure (at least in chrome) that the revocation has been fully processed before the main thread tries to fetch the now revoked URL. Bug: 851942 Change-Id: I12e794682dbb5b34dc08fe2a7d398e3ba02aaffa Reviewed-on: https://chromium-review.googlesource.com/1097230 Reviewed-by: Joshua Bell <jsbell@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#566460} -- wpt-commits: 98530fb94412077886e8df96e25bfdcd3ce460d3 wpt-pr: 11477
testing/web-platform/meta/MANIFEST.json
testing/web-platform/tests/FileAPI/url/resources/revoke-helper.js
--- a/testing/web-platform/meta/MANIFEST.json
+++ b/testing/web-platform/meta/MANIFEST.json
@@ -410611,17 +410611,17 @@
    "f32fd217f3f122a6a910f9258d50d006036b2ee2",
    "support"
   ],
   "FileAPI/url/resources/revoke-helper.html": [
    "f558c2c35ba79c9992b0f24e013eb86415e7e6ff",
    "support"
   ],
   "FileAPI/url/resources/revoke-helper.js": [
-   "9946d1d093a3035e4546bff93473ea2925a74130",
+   "0845933180c0319131b12c2d53bf60a961183e7c",
    "support"
   ],
   "FileAPI/url/sandboxed-iframe.html": [
    "b610b4d0f18472d9eb7ba50f68424e8731d9efff",
    "testharness"
   ],
   "FileAPI/url/unicode-origin.sub.html": [
    "59efa25d03f8765d4848d4b4e6310c7740763342",
--- a/testing/web-platform/tests/FileAPI/url/resources/revoke-helper.js
+++ b/testing/web-platform/tests/FileAPI/url/resources/revoke-helper.js
@@ -1,4 +1,9 @@
 self.addEventListener('message', e => {
   URL.revokeObjectURL(e.data.url);
+  // Registering a new object URL will make absolutely sure that the revocation
+  // has propagated. Without this at least in chrome it is possible for the
+  // below postMessage to arrive at its destination before the revocation has
+  // been fully processed.
+  URL.createObjectURL(new Blob([]));
   self.postMessage('revoked');
 });