Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(31)

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/streams/readable-streams/readable-stream-reader-expected.txt

Issue 1885703003: Make testharness.js tests fail on uncaught exceptions (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Recover script changes Created 4 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 CONSOLE ERROR: line 117: Uncaught (in promise) Error: don't say i didn't warn ya
2 CONSOLE ERROR: line 219: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
3 CONSOLE ERROR: line 225: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
4 CONSOLE ERROR: line 239: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
5 CONSOLE ERROR: line 265: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
6 CONSOLE ERROR: line 303: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
7 CONSOLE ERROR: line 356: Uncaught (in promise) undefined
8 CONSOLE ERROR: line 228: Uncaught (in promise) #<Object>
9 CONSOLE ERROR: line 385: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
10 CONSOLE ERROR: line 117: Uncaught (in promise) Error: don't say i didn't warn ya
11 CONSOLE ERROR: line 219: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
12 CONSOLE ERROR: line 225: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
13 CONSOLE ERROR: line 239: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
14 CONSOLE ERROR: line 265: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
15 CONSOLE ERROR: line 303: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
16 CONSOLE ERROR: line 356: Uncaught (in promise) undefined
17 CONSOLE ERROR: line 228: Uncaught (in promise) #<Object>
18 CONSOLE ERROR: line 385: Uncaught (in promise) TypeError: This readable stream r eader has been released and cannot be used to monitor the stream's state
19 This is a testharness.js-based test.
20 PASS Can get the ReadableStreamReader constructor indirectly
21 PASS ReadableStreamReader constructor should get a ReadableStream object as argu ment
22 PASS ReadableStreamReader instances should have the correct list of properties
23 PASS ReadableStreamReader closed should always return the same promise object
24 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via direct construction)
25 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via direct construction)
26 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via getReader)
27 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via getReader)
28 PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed
29 PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored
30 PASS Reading from a reader for an empty stream will wait until a chunk is availa ble
31 PASS cancel() on a reader does not release the reader
32 PASS closed should be fulfilled after stream is closed (.closed access before ac quiring)
33 PASS closed should be rejected after reader releases its lock (multiple stream l ocks)
34 PASS Multiple readers can access the stream in sequence
35 PASS Cannot use an already-released reader to unlock a stream again
36 PASS cancel() on a released reader is a no-op and does not pass through
37 PASS Getting a second reader after erroring the stream and releasing the reader should succeed
38 PASS ReadableStreamReader closed promise should be rejected with undefined if th at is the error
39 PASS ReadableStreamReader: if start rejects with no parameter, it should error t he stream with an undefined error
40 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea mReader closed promise
41 PASS Erroring a ReadableStream before checking closed should reject ReadableStre amReader closed promise
42 PASS Reading twice on a stream that gets closed
43 PASS Reading twice on a closed stream
44 PASS Reading twice on an errored stream
45 PASS Reading twice on a stream that gets errored
46 PASS Untitled
47 PASS Can get the ReadableStreamReader constructor indirectly
48 PASS ReadableStreamReader constructor should get a ReadableStream object as argu ment
49 PASS ReadableStreamReader instances should have the correct list of properties
50 PASS ReadableStreamReader closed should always return the same promise object
51 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via direct construction)
52 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via direct construction)
53 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via getReader)
54 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via getReader)
55 PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed
56 PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored
57 PASS Reading from a reader for an empty stream will wait until a chunk is availa ble
58 PASS cancel() on a reader does not release the reader
59 PASS closed should be fulfilled after stream is closed (.closed access before ac quiring)
60 PASS closed should be rejected after reader releases its lock (multiple stream l ocks)
61 PASS Multiple readers can access the stream in sequence
62 PASS Cannot use an already-released reader to unlock a stream again
63 PASS cancel() on a released reader is a no-op and does not pass through
64 PASS Getting a second reader after erroring the stream and releasing the reader should succeed
65 PASS ReadableStreamReader closed promise should be rejected with undefined if th at is the error
66 PASS ReadableStreamReader: if start rejects with no parameter, it should error t he stream with an undefined error
67 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea mReader closed promise
68 PASS Erroring a ReadableStream before checking closed should reject ReadableStre amReader closed promise
69 PASS Reading twice on a stream that gets closed
70 PASS Reading twice on a closed stream
71 PASS Reading twice on an errored stream
72 PASS Reading twice on a stream that gets errored
73 PASS Can get the ReadableStreamReader constructor indirectly
74 PASS ReadableStreamReader constructor should get a ReadableStream object as argu ment
75 PASS ReadableStreamReader instances should have the correct list of properties
76 PASS ReadableStreamReader closed should always return the same promise object
77 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via direct construction)
78 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via direct construction)
79 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via getReader)
80 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via getReader)
81 PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed
82 PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored
83 PASS Reading from a reader for an empty stream will wait until a chunk is availa ble
84 PASS cancel() on a reader does not release the reader
85 PASS closed should be fulfilled after stream is closed (.closed access before ac quiring)
86 PASS closed should be rejected after reader releases its lock (multiple stream l ocks)
87 PASS Multiple readers can access the stream in sequence
88 PASS Cannot use an already-released reader to unlock a stream again
89 PASS cancel() on a released reader is a no-op and does not pass through
90 PASS Getting a second reader after erroring the stream and releasing the reader should succeed
91 PASS ReadableStreamReader closed promise should be rejected with undefined if th at is the error
92 PASS ReadableStreamReader: if start rejects with no parameter, it should error t he stream with an undefined error
93 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea mReader closed promise
94 PASS Erroring a ReadableStream before checking closed should reject ReadableStre amReader closed promise
95 PASS Reading twice on a stream that gets closed
96 PASS Reading twice on a closed stream
97 PASS Reading twice on an errored stream
98 PASS Reading twice on a stream that gets errored
99 PASS Can get the ReadableStreamReader constructor indirectly
100 PASS ReadableStreamReader constructor should get a ReadableStream object as argu ment
101 PASS ReadableStreamReader instances should have the correct list of properties
102 PASS ReadableStreamReader closed should always return the same promise object
103 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via direct construction)
104 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via direct construction)
105 PASS Constructing a ReadableStreamReader directly should fail if the stream is a lready locked (via getReader)
106 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a lready locked (via getReader)
107 PASS Constructing a ReadableStreamReader directly should be OK if the stream is closed
108 PASS Constructing a ReadableStreamReader directly should be OK if the stream is errored
109 PASS Reading from a reader for an empty stream will wait until a chunk is availa ble
110 PASS cancel() on a reader does not release the reader
111 PASS closed should be fulfilled after stream is closed (.closed access before ac quiring)
112 PASS closed should be rejected after reader releases its lock (multiple stream l ocks)
113 PASS Multiple readers can access the stream in sequence
114 PASS Cannot use an already-released reader to unlock a stream again
115 PASS cancel() on a released reader is a no-op and does not pass through
116 PASS Getting a second reader after erroring the stream and releasing the reader should succeed
117 PASS ReadableStreamReader closed promise should be rejected with undefined if th at is the error
118 PASS ReadableStreamReader: if start rejects with no parameter, it should error t he stream with an undefined error
119 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea mReader closed promise
120 PASS Erroring a ReadableStream before checking closed should reject ReadableStre amReader closed promise
121 PASS Reading twice on a stream that gets closed
122 PASS Reading twice on a closed stream
123 PASS Reading twice on an errored stream
124 PASS Reading twice on a stream that gets errored
125 Harness: the test ran to completion.
126
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698