RESOLVED FIXED 153277
CSP: Merge from Blink many new tests and changes to existing tests
https://bugs.webkit.org/show_bug.cgi?id=153277
Summary CSP: Merge from Blink many new tests and changes to existing tests
Daniel Bates
Reported 2016-01-20 10:13:17 PST
We should merge many of the Blink Content Security Policy tests to improve our test coverage.
Attachments
Layout Tests (421.85 KB, patch)
2016-01-20 10:32 PST, Daniel Bates
bfulgham: review+
buildbot: commit-queue-
Archive of layout-test-results from ews103 for mac-yosemite (732.10 KB, application/zip)
2016-01-20 11:26 PST, Build Bot
no flags
Archive of layout-test-results from ews105 for mac-yosemite-wk2 (915.35 KB, application/zip)
2016-01-20 11:29 PST, Build Bot
no flags
Archive of layout-test-results from ews117 for mac-yosemite (780.39 KB, application/zip)
2016-01-20 11:36 PST, Build Bot
no flags
Radar WebKit Bug Importer
Comment 1 2016-01-20 10:29:07 PST
Daniel Bates
Comment 2 2016-01-20 10:32:01 PST
Created attachment 269357 [details] Layout Tests
Brent Fulgham
Comment 3 2016-01-20 10:49:14 PST
Comment on attachment 269357 [details] Layout Tests View in context: https://bugs.webkit.org/attachment.cgi?id=269357&action=review r=me. This is all just a snapshot of a moment in time, so I'm not that concerned with the actual test output -- but please double-check that the missing "sourceFile" values and line/column numbers are expected. > LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-cross-origin-image-expected.txt:-16 > -PASS window.e.lineNumber is 23 Why are these expected to have no "sourceFIle" or "lineNumber" values? is that what upstream Blink has for its test results? This seems like a regression from existing behavior.
Daniel Bates
Comment 4 2016-01-20 11:11:59 PST
(In reply to comment #3) > Comment on attachment 269357 [details] > Layout Tests > > View in context: > https://bugs.webkit.org/attachment.cgi?id=269357&action=review > > r=me. This is all just a snapshot of a moment in time, so I'm not that > concerned with the actual test output -- but please double-check that the > missing "sourceFile" values and line/column numbers are expected. > > > LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-cross-origin-image-expected.txt:-16 > > -PASS window.e.lineNumber is 23 > > Why are these expected to have no "sourceFIle" or "lineNumber" values? is > that what upstream Blink has for its test results? Will revert sourceFile and lineNumber changes to the following files before landing: LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-cross-origin-image-expected.txt LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-cross-origin-image-from-script-expected.txt LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-cross-origin-image-from-script.html LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-cross-origin-image.html LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-image-expected.txt LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-image-from-script-expected.txt LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-image-from-script.html LayoutTests/http/tests/security/contentSecurityPolicy/1.1/securitypolicyviolation-block-image.html The changes to sourceFile and lineNumber properties of the stack trace in the above files reflect the changes committed to Blink as of the time of writing. These changes are fall out from the patch for issue <https://codereview.chromium.org/200923002> and are recognized as such in its commit message "Unfortunately, this means that some exceptions no longer have a stack trace". > This seems like a regression from existing behavior. You're right! It is a regression from existing behavior. Will revert sourceFile and lineNumber in the aforementioned files.
Build Bot
Comment 5 2016-01-20 11:26:53 PST
Comment on attachment 269357 [details] Layout Tests Attachment 269357 [details] did not pass mac-ews (mac): Output: http://webkit-queues.webkit.org/results/717980 New failing tests: http/tests/security/xssAuditor/report-script-tag-full-block.html
Build Bot
Comment 6 2016-01-20 11:26:58 PST
Created attachment 269366 [details] Archive of layout-test-results from ews103 for mac-yosemite The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: ews103 Port: mac-yosemite Platform: Mac OS X 10.10.5
Build Bot
Comment 7 2016-01-20 11:29:25 PST
Comment on attachment 269357 [details] Layout Tests Attachment 269357 [details] did not pass mac-wk2-ews (mac-wk2): Output: http://webkit-queues.webkit.org/results/717983 New failing tests: http/tests/security/xssAuditor/report-script-tag-full-block.html
Build Bot
Comment 8 2016-01-20 11:29:30 PST
Created attachment 269367 [details] Archive of layout-test-results from ews105 for mac-yosemite-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: ews105 Port: mac-yosemite-wk2 Platform: Mac OS X 10.10.5
Build Bot
Comment 9 2016-01-20 11:36:43 PST
Comment on attachment 269357 [details] Layout Tests Attachment 269357 [details] did not pass mac-debug-ews (mac): Output: http://webkit-queues.webkit.org/results/717971 New failing tests: http/tests/security/xssAuditor/report-script-tag-full-block.html
Build Bot
Comment 10 2016-01-20 11:36:48 PST
Created attachment 269368 [details] Archive of layout-test-results from ews117 for mac-yosemite The attached test failures were seen while running run-webkit-tests on the mac-debug-ews. Bot: ews117 Port: mac-yosemite Platform: Mac OS X 10.10.5
Daniel Bates
Comment 11 2016-01-20 12:59:53 PST
Michael Catanzaro
Comment 12 2016-01-29 21:01:26 PST
A few of these tests are failing strangely for GTK, see bug #153697.
Note You need to log in before you can comment on or make changes to this bug.