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

Unified Diff: third_party/WebKit/LayoutTests/http/tests/streams/byte-length-queuing-strategy-expected.txt

Issue 2808853003: Remove Blink copies of readable-streams layout tests (Closed)
Patch Set: Restore rs-utils.js as it is used by fetch tests Created 3 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 side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/LayoutTests/http/tests/streams/byte-length-queuing-strategy-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/streams/byte-length-queuing-strategy-expected.txt b/third_party/WebKit/LayoutTests/http/tests/streams/byte-length-queuing-strategy-expected.txt
deleted file mode 100644
index e8270f316bf02cd5043907eb84b900609392abe2..0000000000000000000000000000000000000000
--- a/third_party/WebKit/LayoutTests/http/tests/streams/byte-length-queuing-strategy-expected.txt
+++ /dev/null
@@ -1,33 +0,0 @@
-This is a testharness.js-based test.
-Harness Error. harness_status.status = 1 , harness_status.message = 7 duplicate test names: "Can construct a ByteLengthQueuingStrategy with a valid high water mark", "Can construct a ByteLengthQueuingStrategy with any value as its high water mark", "ByteLengthQueuingStrategy constructor behaves as expected with strange arguments", "ByteLengthQueuingStrategy size behaves as expected with strange arguments", "ByteLengthQueuingStrategy.prototype.size should work generically on its this and its arguments", "ByteLengthQueuingStrategy instances have the correct properties", "ByteLengthQueuingStrategy's highWaterMark property can be set to anything"
-PASS Can construct a ByteLengthQueuingStrategy with a valid high water mark
-PASS Can construct a ByteLengthQueuingStrategy with any value as its high water mark
-PASS ByteLengthQueuingStrategy constructor behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy size behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy.prototype.size should work generically on its this and its arguments
-PASS ByteLengthQueuingStrategy instances have the correct properties
-PASS ByteLengthQueuingStrategy's highWaterMark property can be set to anything
-PASS Untitled
-PASS Can construct a ByteLengthQueuingStrategy with a valid high water mark
-PASS Can construct a ByteLengthQueuingStrategy with any value as its high water mark
-PASS ByteLengthQueuingStrategy constructor behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy size behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy.prototype.size should work generically on its this and its arguments
-PASS ByteLengthQueuingStrategy instances have the correct properties
-PASS ByteLengthQueuingStrategy's highWaterMark property can be set to anything
-PASS Can construct a ByteLengthQueuingStrategy with a valid high water mark
-PASS Can construct a ByteLengthQueuingStrategy with any value as its high water mark
-PASS ByteLengthQueuingStrategy constructor behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy size behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy.prototype.size should work generically on its this and its arguments
-PASS ByteLengthQueuingStrategy instances have the correct properties
-PASS ByteLengthQueuingStrategy's highWaterMark property can be set to anything
-PASS Can construct a ByteLengthQueuingStrategy with a valid high water mark
-PASS Can construct a ByteLengthQueuingStrategy with any value as its high water mark
-PASS ByteLengthQueuingStrategy constructor behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy size behaves as expected with strange arguments
-PASS ByteLengthQueuingStrategy.prototype.size should work generically on its this and its arguments
-PASS ByteLengthQueuingStrategy instances have the correct properties
-PASS ByteLengthQueuingStrategy's highWaterMark property can be set to anything
-Harness: the test ran to completion.
-

Powered by Google App Engine
This is Rietveld 408576698