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

Issues Search
    My Issues | Starred     Open | Closed | All

Unified Diff: LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-expected.txt

Issue 26770004: Add console message levels to test expectation output. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Tests. Created 7 years, 2 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
« no previous file with comments | « LayoutTests/http/tests/websocket/tests/hybi/broken-utf8-expected.txt ('k') | LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-in-busy-expected.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-expected.txt
diff --git a/LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-expected.txt b/LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-expected.txt
index f54dcb8d5a686c838a1316ecc8fb85f6d19edcbf..2ef350f7a21b60897d887f9b8d75db264e8f93fc 100644
--- a/LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-expected.txt
+++ b/LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-expected.txt
@@ -1,22 +1,22 @@
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
-CONSOLE MESSAGE: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
+CONSOLE ERROR: WebSocket is already in CLOSING or CLOSED state.
Web Socket bufferedAmount after closed
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
« no previous file with comments | « LayoutTests/http/tests/websocket/tests/hybi/broken-utf8-expected.txt ('k') | LayoutTests/http/tests/websocket/tests/hybi/bufferedAmount-after-close-in-busy-expected.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698