Make testharness.js tests fail on uncaught exceptions

third_party/WebKit/LayoutTests/http/tests/streams/readable-streams/readable-stream-reader-expected.txt

Index: third_party/WebKit/LayoutTests/http/tests/streams/readable-streams/readable-stream-reader-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/streams/readable-streams/readable-stream-reader-expected.txt b/third_party/WebKit/LayoutTests/http/tests/streams/readable-streams/readable-stream-reader-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..02326a00f259e8c0edb96f6775640c8e41c5dfbc
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/streams/readable-streams/readable-stream-reader-expected.txt
@@ -0,0 +1,126 @@
+CONSOLE ERROR: line 117: Uncaught (in promise) Error: don't say i didn't warn ya
+CONSOLE ERROR: line 219: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 225: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 239: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 265: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 303: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 356: Uncaught (in promise) undefined
+CONSOLE ERROR: line 228: Uncaught (in promise) #<Object>
+CONSOLE ERROR: line 385: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 117: Uncaught (in promise) Error: don't say i didn't warn ya
+CONSOLE ERROR: line 219: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 225: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 239: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 265: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 303: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+CONSOLE ERROR: line 356: Uncaught (in promise) undefined
+CONSOLE ERROR: line 228: Uncaught (in promise) #<Object>
+CONSOLE ERROR: line 385: Uncaught (in promise) TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
+This is a testharness.js-based test.
+PASS Can get the ReadableStreamReader constructor indirectly 
+PASS ReadableStreamReader constructor should get a ReadableStream object as argument 
+PASS ReadableStreamReader instances should have the correct list of properties 
+PASS ReadableStreamReader closed should always return the same promise object 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via direct construction) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via direct construction) 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via getReader) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via getReader) 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored 
+PASS Reading from a reader for an empty stream will wait until a chunk is available 
+PASS cancel() on a reader does not release the reader 
+PASS closed should be fulfilled after stream is closed (.closed access before acquiring) 
+PASS closed should be rejected after reader releases its lock (multiple stream locks) 
+PASS Multiple readers can access the stream in sequence 
+PASS Cannot use an already-released reader to unlock a stream again 
+PASS cancel() on a released reader is a no-op and does not pass through 
+PASS Getting a second reader after erroring the stream and releasing the reader should succeed 
+PASS ReadableStreamReader closed promise should be rejected with undefined if that is the error 
+PASS ReadableStreamReader: if start rejects with no parameter, it should error the stream with an undefined error 
+PASS Erroring a ReadableStream after checking closed should reject ReadableStreamReader closed promise 
+PASS Erroring a ReadableStream before checking closed should reject ReadableStreamReader closed promise 
+PASS Reading twice on a stream that gets closed 
+PASS Reading twice on a closed stream 
+PASS Reading twice on an errored stream 
+PASS Reading twice on a stream that gets errored 
+PASS Untitled 
+PASS Can get the ReadableStreamReader constructor indirectly 
+PASS ReadableStreamReader constructor should get a ReadableStream object as argument 
+PASS ReadableStreamReader instances should have the correct list of properties 
+PASS ReadableStreamReader closed should always return the same promise object 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via direct construction) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via direct construction) 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via getReader) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via getReader) 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored 
+PASS Reading from a reader for an empty stream will wait until a chunk is available 
+PASS cancel() on a reader does not release the reader 
+PASS closed should be fulfilled after stream is closed (.closed access before acquiring) 
+PASS closed should be rejected after reader releases its lock (multiple stream locks) 
+PASS Multiple readers can access the stream in sequence 
+PASS Cannot use an already-released reader to unlock a stream again 
+PASS cancel() on a released reader is a no-op and does not pass through 
+PASS Getting a second reader after erroring the stream and releasing the reader should succeed 
+PASS ReadableStreamReader closed promise should be rejected with undefined if that is the error 
+PASS ReadableStreamReader: if start rejects with no parameter, it should error the stream with an undefined error 
+PASS Erroring a ReadableStream after checking closed should reject ReadableStreamReader closed promise 
+PASS Erroring a ReadableStream before checking closed should reject ReadableStreamReader closed promise 
+PASS Reading twice on a stream that gets closed 
+PASS Reading twice on a closed stream 
+PASS Reading twice on an errored stream 
+PASS Reading twice on a stream that gets errored 
+PASS Can get the ReadableStreamReader constructor indirectly 
+PASS ReadableStreamReader constructor should get a ReadableStream object as argument 
+PASS ReadableStreamReader instances should have the correct list of properties 
+PASS ReadableStreamReader closed should always return the same promise object 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via direct construction) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via direct construction) 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via getReader) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via getReader) 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored 
+PASS Reading from a reader for an empty stream will wait until a chunk is available 
+PASS cancel() on a reader does not release the reader 
+PASS closed should be fulfilled after stream is closed (.closed access before acquiring) 
+PASS closed should be rejected after reader releases its lock (multiple stream locks) 
+PASS Multiple readers can access the stream in sequence 
+PASS Cannot use an already-released reader to unlock a stream again 
+PASS cancel() on a released reader is a no-op and does not pass through 
+PASS Getting a second reader after erroring the stream and releasing the reader should succeed 
+PASS ReadableStreamReader closed promise should be rejected with undefined if that is the error 
+PASS ReadableStreamReader: if start rejects with no parameter, it should error the stream with an undefined error 
+PASS Erroring a ReadableStream after checking closed should reject ReadableStreamReader closed promise 
+PASS Erroring a ReadableStream before checking closed should reject ReadableStreamReader closed promise 
+PASS Reading twice on a stream that gets closed 
+PASS Reading twice on a closed stream 
+PASS Reading twice on an errored stream 
+PASS Reading twice on a stream that gets errored 
+PASS Can get the ReadableStreamReader constructor indirectly 
+PASS ReadableStreamReader constructor should get a ReadableStream object as argument 
+PASS ReadableStreamReader instances should have the correct list of properties 
+PASS ReadableStreamReader closed should always return the same promise object 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via direct construction) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via direct construction) 
+PASS Constructing a ReadableStreamReader directly should fail if the stream is already locked (via getReader) 
+PASS Getting a ReadableStreamReader via getReader should fail if the stream is already locked (via getReader) 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed 
+PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored 
+PASS Reading from a reader for an empty stream will wait until a chunk is available 
+PASS cancel() on a reader does not release the reader 
+PASS closed should be fulfilled after stream is closed (.closed access before acquiring) 
+PASS closed should be rejected after reader releases its lock (multiple stream locks) 
+PASS Multiple readers can access the stream in sequence 
+PASS Cannot use an already-released reader to unlock a stream again 
+PASS cancel() on a released reader is a no-op and does not pass through 
+PASS Getting a second reader after erroring the stream and releasing the reader should succeed 
+PASS ReadableStreamReader closed promise should be rejected with undefined if that is the error 
+PASS ReadableStreamReader: if start rejects with no parameter, it should error the stream with an undefined error 
+PASS Erroring a ReadableStream after checking closed should reject ReadableStreamReader closed promise 
+PASS Erroring a ReadableStream before checking closed should reject ReadableStreamReader closed promise 
+PASS Reading twice on a stream that gets closed 
+PASS Reading twice on a closed stream 
+PASS Reading twice on an errored stream 
+PASS Reading twice on a stream that gets errored 
+Harness: the test ran to completion.
+