RESOLVED DUPLICATE of bug 126240 126238
REGRESSION (r161033): http/tests/security/cross-frame-access-put.html fails
https://bugs.webkit.org/show_bug.cgi?id=126238
Summary REGRESSION (r161033): http/tests/security/cross-frame-access-put.html fails
Alexey Proskuryakov
Reported 2013-12-25 15:53:36 PST
http/tests/security/cross-frame-access-put.html started to fail: http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2Fsecurity%2Fcross-frame-access-put.html --- /Volumes/Data/slave/mountainlion-release-tests-wk1/build/layout-test-results/http/tests/security/cross-frame-access-put-expected.txt +++ /Volumes/Data/slave/mountainlion-release-tests-wk1/build/layout-test-results/http/tests/security/cross-frame-access-put-actual.txt @@ -1,5 +1,4 @@ CONSOLE MESSAGE: Blocked a frame with origin "http://localhost:8000" from accessing a frame with origin "http://127.0.0.1:8000". Protocols, domains, and ports must match. -CONSOLE MESSAGE: Blocked a frame with origin "http://127.0.0.1:8000" from accessing a frame with origin "http://localhost:8000". Protocols, domains, and ports must match. CONSOLE MESSAGE: Blocked a frame with origin "http://127.0.0.1:8000" from accessing a frame with origin "http://localhost:8000". Protocols, domains, and ports must match. CONSOLE MESSAGE: Blocked a frame with origin "http://127.0.0.1:8000" from accessing a frame with origin "http://localhost:8000". Protocols, domains, and ports must match. CONSOLE MESSAGE: Blocked a frame with origin "http://127.0.0.1:8000" from accessing a frame with origin "http://localhost:8000". Protocols, domains, and ports must match. @@ -381,5 +380,6 @@ This test checks cross-frame access security of window attribute setters (rdar://problem/5326791). +PASS: Unable to set property constructor: TypeError: Type error MAIN WINDOW: !!-- Test ended--!!
Attachments
Alexey Proskuryakov
Comment 1 2013-12-25 15:56:11 PST
Marked as failing in http://trac.webkit.org/r161074
Alexey Proskuryakov
Comment 2 2013-12-25 15:57:50 PST
Alexey Proskuryakov
Comment 3 2013-12-25 16:25:19 PST
Resolving via rollout per Oliver's suggestion. *** This bug has been marked as a duplicate of bug 126240 ***
Note You need to log in before you can comment on or make changes to this bug.