Tracking _expected_ WritableStream test failures on the M59 branch |
|||
Issue descriptionThe 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.
,
Apr 20 2017
,
Aug 8 2017
The NextAction date has arrived: 2017-08-08
,
Aug 8 2017
Thank you monorail. The stable branch is now M-60, so this issue is obsolete. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ricea@chromium.org
, Apr 20 2017Labels: M-59 OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows
NextAction: 2017-08-08