| OLD | NEW |
|---|
| (Empty) |
| 1 This is a testharness.js-based test. | |
| 2 Harness Error. harness_status.status = 1 , harness_status.message = 26 duplicate
test names: "Can get the ReadableStreamReader constructor indirectly", "Readabl
eStreamReader constructor should get a ReadableStream object as argument", "Read
ableStreamReader instances should have the correct list of properties", "Readabl
eStreamReader closed should always return the same promise object", "Constructin
g a ReadableStreamReader directly should fail if the stream is already locked (v
ia direct construction)", "Getting a ReadableStreamReader via getReader should f
ail if the stream is already locked (via direct construction)", "Constructing a
ReadableStreamReader directly should fail if the stream is already locked (via g
etReader)", "Getting a ReadableStreamReader via getReader should fail if the str
eam is already locked (via getReader)", "Constructing a ReadableStreamReader dir
ectly should be OK if the stream is closed", "Constructing a ReadableStreamReade
r directly should be OK if the stream is errored", "Reading from a reader for an
empty stream will wait until a chunk is available", "cancel() on a reader does
not release the reader", "closed should be fulfilled after stream is closed (.cl
osed access before acquiring)", "closed should be rejected after reader releases
its lock (multiple stream locks)", "Multiple readers can access the stream in s
equence", "Cannot use an already-released reader to unlock a stream again", "can
cel() on a released reader is a no-op and does not pass through", "Getting a sec
ond reader after erroring the stream and releasing the reader should succeed", "
ReadableStreamReader closed promise should be rejected with undefined if that is
the error", "ReadableStreamReader: if start rejects with no parameter, it shoul
d error the stream with an undefined error", "Erroring a ReadableStream after ch
ecking closed should reject ReadableStreamReader closed promise", "Erroring a Re
adableStream before checking closed should reject ReadableStreamReader closed pr
omise", "Reading twice on a stream that gets closed", "Reading twice on a closed
stream", "Reading twice on an errored stream", "Reading twice on a stream that
gets errored" | |
| 3 PASS Can get the ReadableStreamReader constructor indirectly | |
| 4 PASS ReadableStreamReader constructor should get a ReadableStream object as argu
ment | |
| 5 PASS ReadableStreamReader instances should have the correct list of properties | |
| 6 PASS ReadableStreamReader closed should always return the same promise object | |
| 7 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via direct construction) | |
| 8 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via direct construction) | |
| 9 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via getReader) | |
| 10 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via getReader) | |
| 11 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
closed | |
| 12 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
errored | |
| 13 PASS Reading from a reader for an empty stream will wait until a chunk is availa
ble | |
| 14 PASS cancel() on a reader does not release the reader | |
| 15 PASS closed should be fulfilled after stream is closed (.closed access before ac
quiring) | |
| 16 PASS closed should be rejected after reader releases its lock (multiple stream l
ocks) | |
| 17 PASS Multiple readers can access the stream in sequence | |
| 18 PASS Cannot use an already-released reader to unlock a stream again | |
| 19 PASS cancel() on a released reader is a no-op and does not pass through | |
| 20 PASS Getting a second reader after erroring the stream and releasing the reader
should succeed | |
| 21 PASS ReadableStreamReader closed promise should be rejected with undefined if th
at is the error | |
| 22 PASS ReadableStreamReader: if start rejects with no parameter, it should error t
he stream with an undefined error | |
| 23 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea
mReader closed promise | |
| 24 PASS Erroring a ReadableStream before checking closed should reject ReadableStre
amReader closed promise | |
| 25 PASS Reading twice on a stream that gets closed | |
| 26 PASS Reading twice on a closed stream | |
| 27 PASS Reading twice on an errored stream | |
| 28 PASS Reading twice on a stream that gets errored | |
| 29 PASS Untitled | |
| 30 PASS Can get the ReadableStreamReader constructor indirectly | |
| 31 PASS ReadableStreamReader constructor should get a ReadableStream object as argu
ment | |
| 32 PASS ReadableStreamReader instances should have the correct list of properties | |
| 33 PASS ReadableStreamReader closed should always return the same promise object | |
| 34 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via direct construction) | |
| 35 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via direct construction) | |
| 36 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via getReader) | |
| 37 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via getReader) | |
| 38 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
closed | |
| 39 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
errored | |
| 40 PASS Reading from a reader for an empty stream will wait until a chunk is availa
ble | |
| 41 PASS cancel() on a reader does not release the reader | |
| 42 PASS closed should be fulfilled after stream is closed (.closed access before ac
quiring) | |
| 43 PASS closed should be rejected after reader releases its lock (multiple stream l
ocks) | |
| 44 PASS Multiple readers can access the stream in sequence | |
| 45 PASS Cannot use an already-released reader to unlock a stream again | |
| 46 PASS cancel() on a released reader is a no-op and does not pass through | |
| 47 PASS Getting a second reader after erroring the stream and releasing the reader
should succeed | |
| 48 PASS ReadableStreamReader closed promise should be rejected with undefined if th
at is the error | |
| 49 PASS ReadableStreamReader: if start rejects with no parameter, it should error t
he stream with an undefined error | |
| 50 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea
mReader closed promise | |
| 51 PASS Erroring a ReadableStream before checking closed should reject ReadableStre
amReader closed promise | |
| 52 PASS Reading twice on a stream that gets closed | |
| 53 PASS Reading twice on a closed stream | |
| 54 PASS Reading twice on an errored stream | |
| 55 PASS Reading twice on a stream that gets errored | |
| 56 PASS Can get the ReadableStreamReader constructor indirectly | |
| 57 PASS ReadableStreamReader constructor should get a ReadableStream object as argu
ment | |
| 58 PASS ReadableStreamReader instances should have the correct list of properties | |
| 59 PASS ReadableStreamReader closed should always return the same promise object | |
| 60 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via direct construction) | |
| 61 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via direct construction) | |
| 62 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via getReader) | |
| 63 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via getReader) | |
| 64 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
closed | |
| 65 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
errored | |
| 66 PASS Reading from a reader for an empty stream will wait until a chunk is availa
ble | |
| 67 PASS cancel() on a reader does not release the reader | |
| 68 PASS closed should be fulfilled after stream is closed (.closed access before ac
quiring) | |
| 69 PASS closed should be rejected after reader releases its lock (multiple stream l
ocks) | |
| 70 PASS Multiple readers can access the stream in sequence | |
| 71 PASS Cannot use an already-released reader to unlock a stream again | |
| 72 PASS cancel() on a released reader is a no-op and does not pass through | |
| 73 PASS Getting a second reader after erroring the stream and releasing the reader
should succeed | |
| 74 PASS ReadableStreamReader closed promise should be rejected with undefined if th
at is the error | |
| 75 PASS ReadableStreamReader: if start rejects with no parameter, it should error t
he stream with an undefined error | |
| 76 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea
mReader closed promise | |
| 77 PASS Erroring a ReadableStream before checking closed should reject ReadableStre
amReader closed promise | |
| 78 PASS Reading twice on a stream that gets closed | |
| 79 PASS Reading twice on a closed stream | |
| 80 PASS Reading twice on an errored stream | |
| 81 PASS Reading twice on a stream that gets errored | |
| 82 PASS Can get the ReadableStreamReader constructor indirectly | |
| 83 PASS ReadableStreamReader constructor should get a ReadableStream object as argu
ment | |
| 84 PASS ReadableStreamReader instances should have the correct list of properties | |
| 85 PASS ReadableStreamReader closed should always return the same promise object | |
| 86 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via direct construction) | |
| 87 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via direct construction) | |
| 88 PASS Constructing a ReadableStreamReader directly should fail if the stream is a
lready locked (via getReader) | |
| 89 PASS Getting a ReadableStreamReader via getReader should fail if the stream is a
lready locked (via getReader) | |
| 90 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
closed | |
| 91 PASS Constructing a ReadableStreamReader directly should be OK if the stream is
errored | |
| 92 PASS Reading from a reader for an empty stream will wait until a chunk is availa
ble | |
| 93 PASS cancel() on a reader does not release the reader | |
| 94 PASS closed should be fulfilled after stream is closed (.closed access before ac
quiring) | |
| 95 PASS closed should be rejected after reader releases its lock (multiple stream l
ocks) | |
| 96 PASS Multiple readers can access the stream in sequence | |
| 97 PASS Cannot use an already-released reader to unlock a stream again | |
| 98 PASS cancel() on a released reader is a no-op and does not pass through | |
| 99 PASS Getting a second reader after erroring the stream and releasing the reader
should succeed | |
| 100 PASS ReadableStreamReader closed promise should be rejected with undefined if th
at is the error | |
| 101 PASS ReadableStreamReader: if start rejects with no parameter, it should error t
he stream with an undefined error | |
| 102 PASS Erroring a ReadableStream after checking closed should reject ReadableStrea
mReader closed promise | |
| 103 PASS Erroring a ReadableStream before checking closed should reject ReadableStre
amReader closed promise | |
| 104 PASS Reading twice on a stream that gets closed | |
| 105 PASS Reading twice on a closed stream | |
| 106 PASS Reading twice on an errored stream | |
| 107 PASS Reading twice on a stream that gets errored | |
| 108 Harness: the test ran to completion. | |
| 109 | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2808853003:
Remove Blink copies of readable-streams layout tests (Closed)
