Bug 207792

Summary: Flaky Test: http/tests/appcache/404-resource-with-slow-main-resource.php
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: Tools / TestsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, Hironori.Fujii
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 2020-02-14 14:29:35 PST
This is an automatically generated bug from the commit-queue. http/tests/appcache/404-resource-with-slow-main-resource.php has been flaky on the commit-queue. http/tests/appcache/404-resource-with-slow-main-resource.php was authored by ap@webkit.org and hironori.fujii@sony.com. https://trac.webkit.org/browser/trunk/LayoutTests/http/tests/appcache/404-resource-with-slow-main-resource.php The commit-queue just saw http/tests/appcache/404-resource-with-slow-main-resource.php flake (DumpRenderTree crashed) while processing attachment 390719 [details] on bug 207735. Bot: webkit-cq-03 Port: <class 'webkitpy.common.config.ports.MacPort'> Platform: Mac OS X 10.14.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.16 MB, application/zip)
2020-02-14 14:29 PST, WebKit Commit Bot 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2020-02-14 14:29:37 PST
Created attachment 390822 [details] Archive of layout-test-results from webkit-cq-03
Alexey Proskuryakov
Comment 2 2020-02-14 22:31:43 PST
*** This bug has been marked as a duplicate of bug 153503 ***
Note You need to log in before you can comment on or make changes to this bug.