NEW 189723
[macOS WK1] Layout Test http/tests/security/cross-origin-xsl-redirect-BLOCKED.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=189723
Summary [macOS WK1] Layout Test http/tests/security/cross-origin-xsl-redirect-BLOCKED...
Truitt Savell
Reported 2018-09-18 16:33:55 PDT
The following layout test is failing on Mac WK1 http/tests/security/cross-origin-xsl-redirect-BLOCKED.html Probable cause: unknown cause. test is newley flakey. closest revision that made changes to xsl was https://trac.webkit.org/changeset/235935/webkit Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2Fsecurity%2Fcross-origin-xsl-redirect-BLOCKED.html Diff: --- /Volumes/Data/slave/highsierra-debug-tests-wk1/build/layout-test-results/http/tests/security/cross-origin-xsl-redirect-BLOCKED-expected.txt +++ /Volumes/Data/slave/highsierra-debug-tests-wk1/build/layout-test-results/http/tests/security/cross-origin-xsl-redirect-BLOCKED-actual.txt @@ -1,4 +1,4 @@ -CONSOLE MESSAGE: Unsafe attempt to load URL http://localhost:8000/security/resources/forbidden-stylesheet.xsl from origin http://127.0.0.1:8000. Domains, protocols and ports must match. +CONSOLE MESSAGE: line 2: Unsafe attempt to load URL http://localhost:8000/security/resources/forbidden-stylesheet.xsl from origin http://127.0.0.1:8000. Domains, protocols and ports must match. This test loads the XML document in an iframe so that it can call dumpAsText(). This test passes if the iframe below does not contain a message starting with "FAIL". I have no reproduction steps.
Attachments
Radar WebKit Bug Importer
Comment 1 2018-09-20 09:03:05 PDT
Ryan Haddad
Comment 2 2018-10-17 20:35:31 PDT
This is still happening very frequently on macOS WK1 bots. I was able to reproduce this failure with the following: run-webkit-tests http/tests/security/cross-origin-xsl-redirect-BLOCKED.html -1 -fg --iter 100 --no-retry
Ryan Haddad
Comment 3 2018-10-22 16:06:13 PDT
Marked test as flaky in https://trac.webkit.org/r237337
Note You need to log in before you can comment on or make changes to this bug.