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

Unified Diff: third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/start.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/start.https-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/start.https-expected.txt b/third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/start.https-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..881af392d05e658e2fa0b5a800df1aacdd7330fb
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/start.https-expected.txt
@@ -0,0 +1,25 @@
+This is a testharness.js-based test.
+Harness Error. harness_status.status = 1 , harness_status.message = 5 duplicate test names: "underlying sink's write should not be called until start finishes", "underlying sink's close should not be called until start finishes", "underlying sink's write or close should not be called if start throws", "underlying sink's write or close should not be invoked if the promise returned by start is rejected", "returning a thenable from start() should work"
+PASS underlying sink's write should not be called until start finishes
+PASS underlying sink's close should not be called until start finishes
+PASS underlying sink's write or close should not be called if start throws
+PASS underlying sink's write or close should not be invoked if the promise returned by start is rejected
+PASS returning a thenable from start() should work
+PASS Untitled
+PASS underlying sink's write should not be called until start finishes
+PASS underlying sink's close should not be called until start finishes
+PASS underlying sink's write or close should not be called if start throws
+PASS underlying sink's write or close should not be invoked if the promise returned by start is rejected
+PASS returning a thenable from start() should work
+PASS underlying sink's write should not be called until start finishes
+PASS underlying sink's close should not be called until start finishes
+PASS underlying sink's write or close should not be called if start throws
+PASS underlying sink's write or close should not be invoked if the promise returned by start is rejected
+PASS returning a thenable from start() should work
+PASS underlying sink's write should not be called until start finishes
+PASS underlying sink's close should not be called until start finishes
+PASS underlying sink's write or close should not be called if start throws
+PASS underlying sink's write or close should not be invoked if the promise returned by start is rejected
+PASS returning a thenable from start() should work
+Harness: the test ran to completion.
+

Powered by Google App Engine
This is Rietveld 408576698