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

Unified Diff: third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/close.https-expected.txt

Issue 2766823003: Fix testharness result parsing, make "Harness error" count as failure. (Closed)
Patch Set: One more test with nondeterministic message order Created 3 years, 9 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 side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/close.https-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/close.https-expected.txt b/third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/close.https-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..125e1d8c960515e38f0a64bd9d6dbe16a897c2fe
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/close.https-expected.txt
@@ -0,0 +1,49 @@
+This is a testharness.js-based test.
+Harness Error. harness_status.status = 1 , harness_status.message = 11 duplicate test names: "fulfillment value of ws.close() call must be undefined even if the underlying sink returns a non-undefined value", "when sink calls error asynchronously while closing, the stream should become errored", "when sink calls error synchronously while closing, the stream should become errored", "when close is called on a WritableStream in writable state, ready should return a fulfilled promise", "when close is called on a WritableStream in waiting state, ready promise should be fulfilled", "when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time", "returning a thenable from close() should work", "releaseLock() should not change the result of sync close()", "releaseLock() should not change the result of async close()", "close() should set state to CLOSED even if writer has detached", "the promise returned by async abort during close should resolve"
+PASS fulfillment value of ws.close() call must be undefined even if the underlying sink returns a non-undefined value
+PASS when sink calls error asynchronously while closing, the stream should become errored
+PASS when sink calls error synchronously while closing, the stream should become errored
+PASS when close is called on a WritableStream in writable state, ready should return a fulfilled promise
+PASS when close is called on a WritableStream in waiting state, ready promise should be fulfilled
+PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
+PASS returning a thenable from close() should work
+PASS releaseLock() should not change the result of sync close()
+PASS releaseLock() should not change the result of async close()
+PASS close() should set state to CLOSED even if writer has detached
+PASS the promise returned by async abort during close should resolve
+PASS Untitled
+PASS fulfillment value of ws.close() call must be undefined even if the underlying sink returns a non-undefined value
+PASS when sink calls error asynchronously while closing, the stream should become errored
+PASS when sink calls error synchronously while closing, the stream should become errored
+PASS when close is called on a WritableStream in writable state, ready should return a fulfilled promise
+PASS when close is called on a WritableStream in waiting state, ready promise should be fulfilled
+PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
+PASS returning a thenable from close() should work
+PASS releaseLock() should not change the result of sync close()
+PASS releaseLock() should not change the result of async close()
+PASS close() should set state to CLOSED even if writer has detached
+PASS the promise returned by async abort during close should resolve
+PASS fulfillment value of ws.close() call must be undefined even if the underlying sink returns a non-undefined value
+PASS when sink calls error asynchronously while closing, the stream should become errored
+PASS when sink calls error synchronously while closing, the stream should become errored
+PASS when close is called on a WritableStream in writable state, ready should return a fulfilled promise
+PASS when close is called on a WritableStream in waiting state, ready promise should be fulfilled
+PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
+PASS returning a thenable from close() should work
+PASS releaseLock() should not change the result of sync close()
+PASS releaseLock() should not change the result of async close()
+PASS close() should set state to CLOSED even if writer has detached
+PASS the promise returned by async abort during close should resolve
+PASS fulfillment value of ws.close() call must be undefined even if the underlying sink returns a non-undefined value
+PASS when sink calls error asynchronously while closing, the stream should become errored
+PASS when sink calls error synchronously while closing, the stream should become errored
+PASS when close is called on a WritableStream in writable state, ready should return a fulfilled promise
+PASS when close is called on a WritableStream in waiting state, ready promise should be fulfilled
+PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
+PASS returning a thenable from close() should work
+PASS releaseLock() should not change the result of sync close()
+PASS releaseLock() should not change the result of async close()
+PASS close() should set state to CLOSED even if writer has detached
+PASS the promise returned by async abort during close should resolve
+Harness: the test ran to completion.
+

Powered by Google App Engine
This is Rietveld 408576698