New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 736732 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit 15 days ago
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

LayoutTest virtual/enable_wasm/external/wpt/wasm/wasm_local_iframe_test.html is flaky

Project Member Reported by yhirano@chromium.org, Jun 26 2017

Issue description

Project Member

Comment 1 by bugdroid1@chromium.org, Jun 26 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/74c13f87407f1a14aa5717103fef4005d0234b3b

commit 74c13f87407f1a14aa5717103fef4005d0234b3b
Author: Yutaka Hirano <yhirano@chromium.org>
Date: Mon Jun 26 11:53:59 2017

Mark virtual/enable_wasm/external/wpt/wasm/wasm_local_iframe_test.html as flaky

Bug:  736732 
Change-Id: I8119e2b5bc81eefcd2b3157cdb04415888a3e43c
Tbr: mtrofin@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/547221
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#482246}
[modify] https://crrev.com/74c13f87407f1a14aa5717103fef4005d0234b3b/third_party/WebKit/LayoutTests/TestExpectations

Comment 2 by jochen@chromium.org, Jun 27 2017

Owner: mtrofin@chromium.org
Status: Assigned (was: Untriaged)
Status: Started (was: Assigned)
Odd. It seems it fails because it tries to fetch incrementer.wasm via the file protocol. 

Comment 4 by binji@chromium.org, Jun 13 2018

Owner: binji@chromium.org
Status: WontFix (was: Started)
Looking at the recent flakiness dashboard, this doesn't seem to be flaky anymore.
Project Member

Comment 5 by bugdroid1@chromium.org, Jun 14 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/148a481a12b1e8cf11d04d5048a8f5b461c90ec2

commit 148a481a12b1e8cf11d04d5048a8f5b461c90ec2
Author: Ben Smith <binji@chromium.org>
Date: Thu Jun 14 21:20:00 2018

[wasm] Update TestExpectations for wasm WPT tests

* wasm_local_iframe_test doesn't appear to be flaky anymore
* The wasm WPT tests all require the --enable-wasm flag, so must be run
  in the virtual/enable_wasm/ testsuite

Bug:  736732 
Change-Id: I6076a5aecdfb018ad81130721062955e2ede8d5c
Reviewed-on: https://chromium-review.googlesource.com/1100078
Reviewed-by: Derek Schuff <dschuff@chromium.org>
Commit-Queue: Ben Smith <binji@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567419}
[modify] https://crrev.com/148a481a12b1e8cf11d04d5048a8f5b461c90ec2/third_party/WebKit/LayoutTests/TestExpectations

Sign in to add a comment