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

Unified Diff: third_party/WebKit/LayoutTests/imported/wpt/html/webappapis/scripting/events/inline-event-handler-ordering-expected.txt

Issue 2052643002: This change modifies testharnessreport (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Fix failing tests Created 4 years, 6 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/imported/wpt/html/webappapis/scripting/events/inline-event-handler-ordering-expected.txt
diff --git a/third_party/WebKit/LayoutTests/imported/wpt/html/webappapis/scripting/events/inline-event-handler-ordering-expected.txt b/third_party/WebKit/LayoutTests/imported/wpt/html/webappapis/scripting/events/inline-event-handler-ordering-expected.txt
index e151657281fc4450a62d6d58d681fb21f78f8499..126ec848c4dc81e6c0ea859379bc9fc1930e4ac3 100644
--- a/third_party/WebKit/LayoutTests/imported/wpt/html/webappapis/scripting/events/inline-event-handler-ordering-expected.txt
+++ b/third_party/WebKit/LayoutTests/imported/wpt/html/webappapis/scripting/events/inline-event-handler-ordering-expected.txt
@@ -2,5 +2,8 @@ CONSOLE ERROR: line 52: Uncaught SyntaxError: Unexpected token }
CONSOLE ERROR: line 52: Uncaught SyntaxError: Unexpected token }
This is a testharness.js-based test.
Harness Error. harness_status.status = 1 , harness_status.message = Uncaught SyntaxError: Unexpected token }
+FAIL Inline event handlers retain their ordering when invalid and force-compiled assert_array_equals: property 1, expected "TWO" but got "THREE"
+FAIL Inline event handlers retain their ordering when invalid and force-compiled via dispatch assert_array_equals: property 3, expected "TWO" but got "THREE"
+FAIL Inline event handlers retain their ordering when invalid and lazy-compiled assert_array_equals: property 1, expected "TWO" but got "THREE"
Harness: the test ran to completion.

Powered by Google App Engine
This is Rietveld 408576698