| Index: third_party/WebKit/LayoutTests/external/wpt/streams/piping/pipe-through.dedicatedworker-expected.txt
|
| diff --git a/third_party/WebKit/LayoutTests/external/wpt/streams/piping/pipe-through.dedicatedworker-expected.txt b/third_party/WebKit/LayoutTests/external/wpt/streams/piping/pipe-through.dedicatedworker-expected.txt
|
| index 0afae02366c5bdc200cf9650db0180ca1e1ae685..7760b92b7e0fa99c8bee58973beefa038bd3994e 100644
|
| --- a/third_party/WebKit/LayoutTests/external/wpt/streams/piping/pipe-through.dedicatedworker-expected.txt
|
| +++ b/third_party/WebKit/LayoutTests/external/wpt/streams/piping/pipe-through.dedicatedworker-expected.txt
|
| @@ -1,4 +1,5 @@
|
| This is a testharness.js-based test.
|
| +Found 5 tests. 0 PASS 5 FAIL 0 TIMEOUT 0 NOTRUN
|
| FAIL Piping through a duck-typed pass-through transform stream should work sequentialReadableStream(...).pipeThrough is not a function
|
| FAIL Piping through a transform errored on the writable end does not cause an unhandled promise rejection sequentialReadableStream(...).pipeThrough is not a function
|
| FAIL pipeThrough generically calls pipeTo with the appropriate args Cannot read property 'call' of undefined
|
|
|