virtual/mojo-blob-urls/external/wpt/FileAPI/url/cross-global-revoke.sub.html is flaky |
||||
Issue descriptionThis test is flaky: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=external%2Fwpt%2FFileAPI%2Furl%2Fcross-global-revoke.sub.html It has made my CQ run sad: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng/115215 Expected: PASS It is possible to revoke same-origin blob URLs from a different worker global. Actual: FAIL It is possible to revoke same-origin blob URLs from a different worker global. assert_unreached: Should have rejected: undefined Reached unreachable code Mek, can you take a look? This may be part of the larger https://crbug.com/800986 but we should disable these tests or mark them as flaky until the underlying issue is fixed.
,
Jun 12 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a885cb4987d3af87314b5c6bb13caf98a1bd2fc3 commit a885cb4987d3af87314b5c6bb13caf98a1bd2fc3 Author: Marijn Kruisselbrink <mek@chromium.org> Date: Tue Jun 12 16:45:19 2018 Fix 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} [modify] https://crrev.com/a885cb4987d3af87314b5c6bb13caf98a1bd2fc3/third_party/WebKit/LayoutTests/external/wpt/FileAPI/url/resources/revoke-helper.js
,
Jun 12 2018
,
Jun 15 2018
,
Jun 15 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by mek@chromium.org
, Jun 12 2018