Update WritableStream to new standard version

third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/start.serviceworker.https-expected.txt

Index: third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/start.serviceworker.https-expected.txt
diff --git a/third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/start.serviceworker.https-expected.txt b/third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/start.serviceworker.https-expected.txt
deleted file mode 100644
index ecf680bffec76c37128a9640bc09ed7c73b016ad..0000000000000000000000000000000000000000
--- a/third_party/WebKit/LayoutTests/external/wpt/streams/writable-streams/start.serviceworker.https-expected.txt
+++ /dev/null
@@ -1,12 +0,0 @@
-This is a testharness.js-based test.
-PASS Service worker test setup 
-PASS underlying sink's write should not be called until start finishes 
-PASS underlying sink's close should not be called until start finishes 
-PASS underlying sink's write or close should not be called if start throws 
-PASS underlying sink's write or close should not be invoked if the promise returned by start is rejected 
-PASS returning a thenable from start() should work 
-FAIL controller.error() during start should cause writes to fail assert_throws: write() should reject with the error function "function () { throw e }" threw object "TypeError: Cannot write to a errored writable stream" ("TypeError") expected object "[object Object]" ("error1")
-PASS controller.error() during async start should cause existing writes to fail 
-FAIL when start() rejects, writer promises should reject in standard order assert_array_equals: promises should reject in standard order property 0, expected "ready" but got "write"
-Harness: the test ran to completion.
-