New issue
Advanced search Search tips

Issue 713664 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-08-08
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Tracking _expected_ WritableStream test failures on the M59 branch

Project Member Reported by ricea@chromium.org, Apr 20 2017

Issue description

The M59 branch contains an up-to-date version of WritableStream with an out-of-date version of the web-platform-tests. 

As a consequence, many WritableStream and piping tests fail on the branch. Most of the failures are caused by an unnecessary check in streams/resources/recording-streams.js that the "controller" argument is passed to close().

The aborting.* and start.* tests timeout due to waiting for events that in the new implementation do not arrive until later.

There is no plan to merge the updated tests to the M59 branch at this time.

This issue exists to track and document the test failures. It can be closed once M60 becomes stable.
 

Comment 1 by ricea@chromium.org, Apr 20 2017

Components: Blink>Network>StreamsAPI
Labels: M-59 OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows
NextAction: 2017-08-08

Comment 2 by ricea@chromium.org, Apr 20 2017

Summary: Tracking _expected_ WritableStream test failures on the M59 branch (was: Failing WritableStream tests on the M59 branch)
The NextAction date has arrived: 2017-08-08

Comment 4 by ricea@chromium.org, Aug 8 2017

Status: WontFix (was: Assigned)
Thank you monorail. The stable branch is now M-60, so this issue is obsolete.

Sign in to add a comment