Commit e939961b authored by Chromium WPT Sync's avatar Chromium WPT Sync Committed by Commit Bot

Import wpt@ea469b6059e82729ef04cd90758fc9b52b733c7f

Using wpt-import in Chromium 02de1dcf.

Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/15340

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
domenic@chromium.org, ricea@chromium.org:
  external/wpt/streams

TBR=ajuma

No-Export: true
Change-Id: I77a008c5077e22979fc93d487960dd93cbe8d0e6
Reviewed-on: https://chromium-review.googlesource.com/992692
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: default avatarBlink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547760}
parent 8ca5c09b
This is a testharness.js-based test.
PASS Can get the ReadableStreamDefaultReader constructor indirectly
PASS ReadableStreamDefaultReader constructor should get a ReadableStream object as argument
PASS ReadableStreamDefaultReader instances should have the correct list of properties
PASS ReadableStreamDefaultReader closed should always return the same promise object
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via direct construction)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via direct construction)
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via getReader)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via getReader)
PASS Constructing a ReadableStreamDefaultReader directly should be OK if the stream is closed
PASS Constructing a ReadableStreamDefaultReader 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 ReadableStreamDefaultReader closed promise should be rejected with undefined if that is the error
PASS ReadableStreamDefaultReader: if start rejects with no parameter, it should error the stream with an undefined error
PASS Erroring a ReadableStream after checking closed should reject ReadableStreamDefaultReader closed promise
PASS Erroring a ReadableStream before checking closed should reject ReadableStreamDefaultReader 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
FAIL getReader() should call ToString() on mode assert_true: toString() should be called expected true got false
Harness: the test ran to completion.
This is a testharness.js-based test.
PASS Can get the ReadableStreamDefaultReader constructor indirectly
PASS ReadableStreamDefaultReader constructor should get a ReadableStream object as argument
PASS ReadableStreamDefaultReader instances should have the correct list of properties
PASS ReadableStreamDefaultReader closed should always return the same promise object
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via direct construction)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via direct construction)
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via getReader)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via getReader)
PASS Constructing a ReadableStreamDefaultReader directly should be OK if the stream is closed
PASS Constructing a ReadableStreamDefaultReader 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 ReadableStreamDefaultReader closed promise should be rejected with undefined if that is the error
PASS ReadableStreamDefaultReader: if start rejects with no parameter, it should error the stream with an undefined error
PASS Erroring a ReadableStream after checking closed should reject ReadableStreamDefaultReader closed promise
PASS Erroring a ReadableStream before checking closed should reject ReadableStreamDefaultReader 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
FAIL getReader() should call ToString() on mode assert_true: toString() should be called expected true got false
Harness: the test ran to completion.
......@@ -485,4 +485,17 @@ promise_test(t => {
}, 'Reading twice on a stream that gets errored');
test(() => {
const rs = new ReadableStream();
let toStringCalled = false;
const mode = {
toString() {
toStringCalled = true;
return '';
}
};
assert_throws(new RangeError(), () => rs.getReader({ mode }), 'getReader() should throw');
assert_true(toStringCalled, 'toString() should be called');
}, 'getReader() should call ToString() on mode');
done();
This is a testharness.js-based test.
PASS Service worker test setup
PASS Can get the ReadableStreamDefaultReader constructor indirectly
PASS ReadableStreamDefaultReader constructor should get a ReadableStream object as argument
PASS ReadableStreamDefaultReader instances should have the correct list of properties
PASS ReadableStreamDefaultReader closed should always return the same promise object
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via direct construction)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via direct construction)
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via getReader)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via getReader)
PASS Constructing a ReadableStreamDefaultReader directly should be OK if the stream is closed
PASS Constructing a ReadableStreamDefaultReader 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 ReadableStreamDefaultReader closed promise should be rejected with undefined if that is the error
PASS ReadableStreamDefaultReader: if start rejects with no parameter, it should error the stream with an undefined error
PASS Erroring a ReadableStream after checking closed should reject ReadableStreamDefaultReader closed promise
PASS Erroring a ReadableStream before checking closed should reject ReadableStreamDefaultReader 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
FAIL getReader() should call ToString() on mode assert_true: toString() should be called expected true got false
Harness: the test ran to completion.
This is a testharness.js-based test.
PASS Can get the ReadableStreamDefaultReader constructor indirectly
PASS ReadableStreamDefaultReader constructor should get a ReadableStream object as argument
PASS ReadableStreamDefaultReader instances should have the correct list of properties
PASS ReadableStreamDefaultReader closed should always return the same promise object
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via direct construction)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via direct construction)
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via getReader)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via getReader)
PASS Constructing a ReadableStreamDefaultReader directly should be OK if the stream is closed
PASS Constructing a ReadableStreamDefaultReader 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 ReadableStreamDefaultReader closed promise should be rejected with undefined if that is the error
PASS ReadableStreamDefaultReader: if start rejects with no parameter, it should error the stream with an undefined error
PASS Erroring a ReadableStream after checking closed should reject ReadableStreamDefaultReader closed promise
PASS Erroring a ReadableStream before checking closed should reject ReadableStreamDefaultReader 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
FAIL getReader() should call ToString() on mode assert_true: toString() should be called expected true got false
Harness: the test ran to completion.
This is a testharness.js-based test.
PASS Can get the ReadableStreamDefaultReader constructor indirectly
PASS ReadableStreamDefaultReader constructor should get a ReadableStream object as argument
PASS ReadableStreamDefaultReader instances should have the correct list of properties
PASS ReadableStreamDefaultReader closed should always return the same promise object
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via direct construction)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via direct construction)
PASS Constructing a ReadableStreamDefaultReader directly should fail if the stream is already locked (via getReader)
PASS Getting a ReadableStreamDefaultReader via getReader should fail if the stream is already locked (via getReader)
PASS Constructing a ReadableStreamDefaultReader directly should be OK if the stream is closed
PASS Constructing a ReadableStreamDefaultReader 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 ReadableStreamDefaultReader closed promise should be rejected with undefined if that is the error
PASS ReadableStreamDefaultReader: if start rejects with no parameter, it should error the stream with an undefined error
PASS Erroring a ReadableStream after checking closed should reject ReadableStreamDefaultReader closed promise
PASS Erroring a ReadableStream before checking closed should reject ReadableStreamDefaultReader 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
FAIL getReader() should call ToString() on mode assert_true: toString() should be called expected true got false
Harness: the test ran to completion.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment