Summary: | [Catalina Release wk1] imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/cross-origin-objects.html is a flaky failure | ||
---|---|---|---|
Product: | WebKit | Reporter: | Eric Hutchison <ehutchison> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | cdumez, ehutchison, webkit-bot-watchers-bugzilla, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Eric Hutchison
2021-09-23 16:02:15 PDT
Updated test expectations at https://trac.webkit.org/changeset/283018/webkit The diff I see on the bots is: --- /Volumes/Data/worker/catalina-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/cross-origin-objects-expected.txt +++ /Volumes/Data/worker/catalina-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/cross-origin-objects-actual.txt @@ -1,3 +1,22 @@ +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, and ports must match. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, and ports must match. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, and ports must match. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://localhost:8800". The frame being accessed set "document.domain" to "localhost", but the frame requesting access did not. Both must set "document.domain" to the same value to allow access. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://localhost:8800". The frame being accessed set "document.domain" to "localhost", but the frame requesting access did not. Both must set "document.domain" to the same value to allow access. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://localhost:8800". The frame being accessed set "document.domain" to "localhost", but the frame requesting access did not. Both must set "document.domain" to the same value to allow access. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, and ports must match. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, and ports must match. +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, and ports must match. +CONSOLE MESSAGE: Unable to post message to http://does-not.exist. Recipient has origin http://127.0.0.1:8800. + +CONSOLE MESSAGE: Unable to post message to http://localhost:8800. Recipient has origin http://127.0.0.1:8800. + +CONSOLE MESSAGE: Unable to post message to http://does-not.exist. Recipient has origin http://127.0.0.1:8800. + +CONSOLE MESSAGE: Unable to post message to http://localhost:8800. Recipient has origin http://127.0.0.1:8800. + +CONSOLE MESSAGE: Unable to post message to http://does-not.exist. Recipient has origin http://localhost:8800. + PASS Basic sanity-checking (cross-origin) PASS Basic sanity-checking (same-origin + document.domain) It is fishy because it is only failing on this one bot AND we have the following line in TestExpectations: imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/cross-origin-objects.html [ DumpJSConsoleLogInStdErr ] So somehow, the [ DumpJSConsoleLogInStdErr ] in TestExpectations is ignored and the test output still contains console messages on this particular bot? (In reply to Chris Dumez from comment #3) > The diff I see on the bots is: > --- > /Volumes/Data/worker/catalina-release-tests-wk1/build/layout-test-results/ > imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/ > cross-origin-objects-expected.txt > +++ > /Volumes/Data/worker/catalina-release-tests-wk1/build/layout-test-results/ > imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/ > cross-origin-objects-actual.txt > @@ -1,3 +1,22 @@ > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, > and ports must match. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, > and ports must match. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, > and ports must match. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://localhost:8800". The frame being > accessed set "document.domain" to "localhost", but the frame requesting > access did not. Both must set "document.domain" to the same value to allow > access. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://localhost:8800". The frame being > accessed set "document.domain" to "localhost", but the frame requesting > access did not. Both must set "document.domain" to the same value to allow > access. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://localhost:8800". The frame being > accessed set "document.domain" to "localhost", but the frame requesting > access did not. Both must set "document.domain" to the same value to allow > access. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, > and ports must match. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, > and ports must match. > +CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8800" from > accessing a frame with origin "http://127.0.0.1:8800". Protocols, domains, > and ports must match. > +CONSOLE MESSAGE: Unable to post message to http://does-not.exist. Recipient > has origin http://127.0.0.1:8800. > + > +CONSOLE MESSAGE: Unable to post message to http://localhost:8800. Recipient > has origin http://127.0.0.1:8800. > + > +CONSOLE MESSAGE: Unable to post message to http://does-not.exist. Recipient > has origin http://127.0.0.1:8800. > + > +CONSOLE MESSAGE: Unable to post message to http://localhost:8800. Recipient > has origin http://127.0.0.1:8800. > + > +CONSOLE MESSAGE: Unable to post message to http://does-not.exist. Recipient > has origin http://localhost:8800. > + > > PASS Basic sanity-checking (cross-origin) > PASS Basic sanity-checking (same-origin + document.domain) > > > It is fishy because it is only failing on this one bot AND we have the > following line in TestExpectations: > imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/ > cross-origin-objects.html [ DumpJSConsoleLogInStdErr ] > > So somehow, the [ DumpJSConsoleLogInStdErr ] in TestExpectations is ignored > and the test output still contains console messages on this particular bot? Or maybe this diff is simply the result of Eric marking this test as flaky here: LayoutTests/platform/mac-wk1/TestExpectations:webkit.org/b/230729 [ Catalina Release ] imported/w3c/web-platform-tests/html/browsers/origin/cross-origin-objects/cross-origin-objects.html [ Pass Failure ] Maybe [ Pass Failure ] in mac-wk1's TestExpectations overrides [ DumpJSConsoleLogInStdErr ] in the global TestExpectations. The test in general is slow and the output from https://bugs.webkit.org/show_bug.cgi?id=230729# seems to indicate that the time is sometimes a little too slow and times out. We may need to mark this test as [ Slow ]. Committed r290891 (?): <https://commits.webkit.org/r290891> |