Bug 203405

Summary: Flaky Test: imported/w3c/web-platform-tests/content-security-policy/navigate-to/href-location-allowed.html
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: Tools / TestsAssignee: WebKit Commit Bot <commit-queue>
Status: NEW    
Severity: Normal CC: ap, dbates
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 50856    
Attachments:
Description Flags
Archive of layout-test-results from webkit-cq-03 none

WebKit Commit Bot
Reported 2019-10-25 04:00:42 PDT
This is an automatically generated bug from the commit-queue. imported/w3c/web-platform-tests/content-security-policy/navigate-to/href-location-allowed.html has been flaky on the commit-queue. imported/w3c/web-platform-tests/content-security-policy/navigate-to/href-location-allowed.html was authored by dbates@webkit.org. https://trac.webkit.org/browser/trunk/LayoutTests/imported/w3c/web-platform-tests/content-security-policy/navigate-to/href-location-allowed.html The commit-queue just saw imported/w3c/web-platform-tests/content-security-policy/navigate-to/href-location-allowed.html flake (text diff) while processing attachment 381895 [details] on bug 203301. Bot: webkit-cq-03 Port: <class 'webkitpy.common.config.ports.MacPort'> Platform: Mac OS X 10.13.6 The bots will update this with information from each new failure. If you believe this bug to be fixed or invalid, feel free to close. The bots will re-open if the flake re-occurs. If you would like to track this test fix with another bug, please close this bug as a duplicate. The bots will follow the duplicate chain when making future comments.
Attachments
Archive of layout-test-results from webkit-cq-03 (3.63 MB, application/zip)
2019-10-25 04:00 PDT, WebKit Commit Bot
no flags
WebKit Commit Bot
Comment 1 2019-10-25 04:00:44 PDT
Created attachment 381905 [details] Archive of layout-test-results from webkit-cq-03
Alexey Proskuryakov
Comment 2 2019-10-27 14:44:27 PDT
This is no happening in post-commit testing at all.
Note You need to log in before you can comment on or make changes to this bug.