Update WritableStream to new standard version

third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/aborting-expected.txt

Index: third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/aborting-expected.txt
diff --git a/third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/aborting-expected.txt b/third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/aborting-expected.txt
deleted file mode 100644
index 1a1910deb8f8376c7679aa530f1d413be0403088..0000000000000000000000000000000000000000
--- a/third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/aborting-expected.txt
+++ /dev/null
@@ -1,44 +0,0 @@
-This is a testharness.js-based test.
-PASS Aborting a WritableStream before it starts should cause the writer's unsettled ready promise to reject 
-PASS Aborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one 
-PASS abort() on a released writer rejects 
-PASS Aborting a WritableStream immediately prevents future writes 
-PASS Aborting a WritableStream prevents further writes after any that are in progress 
-PASS Fulfillment value of ws.abort() call must be undefined even if the underlying sink returns a non-undefined value 
-PASS WritableStream if sink's abort throws, the promise returned by writer.abort() rejects 
-PASS WritableStream if sink's abort throws, the promise returned by ws.abort() rejects 
-PASS WritableStream if sink's abort throws, for an abort performed during a write, the promise returned by ws.abort() rejects 
-PASS Aborting a WritableStream passes through the given reason 
-PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error 
-PASS Aborting a WritableStream causes any outstanding write() promises to be rejected with a TypeError 
-PASS Closing but then immediately aborting a WritableStream causes the stream to error 
-FAIL Closing a WritableStream and aborting it while it closes causes the stream to ignore the abort attempt promise_test: Unhandled rejection with value: object "TypeError: The stream has been aborted"
-PASS Aborting a WritableStream after it is closed is a no-op 
-PASS WritableStream should NOT call underlying sink's close if no abort is supplied (historical) 
-PASS returning a thenable from abort() should work 
-PASS .closed should not resolve before fulfilled write() 
-PASS .closed should not resolve before rejected write(); write() error should overwrite abort() error 
-PASS writes should be satisfied in order when aborting 
-PASS writes should be satisfied in order after rejected write when aborting 
-PASS close() should use error from underlying write() on abort 
-PASS underlying abort() should not be called until underlying write() completes 
-PASS underlying abort() should not be called if underlying close() has started 
-PASS if underlying close() has started and then rejects, the abort() and close() promises should reject with the underlying close rejection reason 
-PASS an abort() that happens during a write() should trigger the underlying abort() even with a close() queued 
-FAIL if a writer is created for a stream with a pending abort, its ready should be rejected with a TypeError assert_unreached: Should have rejected: ready of the second writer should be rejected with a TypeError Reached unreachable code
-PASS writer close() promise should resolve before abort() promise 
-PASS writer.ready should reject on controller error without waiting for underlying write 
-FAIL writer.abort() while there is an in-flight write, and then finish the write with rejection assert_throws: writePromise3 must reject with the error returned from the sink's write method function "function () { throw e }" threw object "TypeError: Cannot write to a errored writable stream" ("TypeError") expected object "error2: error2" ("error2")
-FAIL writer.abort(), controller.error() while there is an in-flight write, and then finish the write promise_test: Unhandled rejection with value: object "TypeError: Cannot error a errored writable stream"
-FAIL controller.error(), writer.abort() while there is an in-flight write, and then finish the write assert_throws: writePromise2 must reject with the error passed to the controller's error method function "function () { throw e }" threw object "TypeError: Cannot write to a errored writable stream" ("TypeError") expected object "error2: error2" ("error2")
-PASS releaseLock() while aborting should reject the original closed promise 
-PASS releaseLock() during delayed async abort() should create a new rejected closed promise 
-FAIL sink abort() should not be called until sink start() is done assert_array_equals: abort() should not be called during start() lengths differ, expected 0 got 2
-FAIL abort() promise should reject if start() errors the controller Cannot error a errored writable stream
-FAIL stream abort() promise should reject if sink start() rejects assert_unreached: Should have rejected: abort() should reject if start() rejects Reached unreachable code
-PASS writer abort() during sink start() should replace the writer.ready promise synchronously 
-FAIL promises returned from other writer methods should be rejected when writer abort() happens during sink start() assert_array_equals: promises should resolve in the standard order property 0, expected "write2" but got "abort"
-FAIL abort() should be rejected with the error passed to controller.error() during pending write() promise_test: Unhandled rejection with value: object "TypeError: Cannot error a errored writable stream"
-FAIL abort() should be rejected with the error passed to controller.error() during pending close() promise_test: Unhandled rejection with value: object "TypeError: Cannot error a errored writable stream"
-Harness: the test ran to completion.
-