Bug 182245

Summary: [WPE] Layout test imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/module/errorhandling.html is failing
Product: WebKit Reporter: Michael Catanzaro <mcatanzaro>
Component: WPE WebKitAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: bugs-noreply, ysuzuki
Priority: P2    
Version: Other   
Hardware: PC   
OS: Linux   

Description Michael Catanzaro 2018-01-29 08:46:18 PST
Layout test imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/module/errorhandling.html is a flaky failure for WPE since its crash expectation was removed in r227649 "imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/module/errorhandling.html crashes". Sometimes the console messages print in a different order. Not sure why:

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/module/errorhandling-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/module/errorhandling-actual.txt
@@ -1,9 +1,9 @@
-CONSOLE MESSAGE: TypeError: 'text/plain' is not a valid JavaScript MIME type.
-CONSOLE MESSAGE: TypeError: 'text/plain' is not a valid JavaScript MIME type.
 CONSOLE MESSAGE: line 1: SyntaxError: No identifiers allowed directly after numeric literal
 CONSOLE MESSAGE: line 1: SyntaxError: No identifiers allowed directly after numeric literal
 CONSOLE MESSAGE: line 1: SyntaxError: No identifiers allowed directly after numeric literal
 CONSOLE MESSAGE: line 1: SyntaxError: No identifiers allowed directly after numeric literal
+CONSOLE MESSAGE: TypeError: 'text/plain' is not a valid JavaScript MIME type.
+CONSOLE MESSAGE: TypeError: 'text/plain' is not a valid JavaScript MIME type.
 html-script-module-errorHandling
Comment 1 Yusuke Suzuki 2018-01-29 23:50:13 PST
This is inherently flaky due to how the test runs. We should have a way to disable console message dump.

*** This bug has been marked as a duplicate of bug 182177 ***