Bug 61591

Summary: Flaky Test: http/tests/xmlhttprequest/access-control-preflight-headers-async.html
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: Tools / TestsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: abarth, annevk, ap
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 50856    
Attachments:
Description Flags
Failure diff from cr-jail-8 none

WebKit Commit Bot
Reported 2011-05-26 19:19:13 PDT
This is an automatically generated bug from the commit-queue. http/tests/xmlhttprequest/access-control-preflight-headers-async.html has been flaky on the commit-queue. http/tests/xmlhttprequest/access-control-preflight-headers-async.html was authored by ap@webkit.org. http://trac.webkit.org/browser/trunk/LayoutTests/http/tests/xmlhttprequest/access-control-preflight-headers-async.html The commit-queue just saw http/tests/xmlhttprequest/access-control-preflight-headers-async.html flake (Text diff mismatch) while processing attachment 94998 [details] on bug 42676. Bot: cr-jail-8 Port: Mac Platform: Mac OS X 10.6.7 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
Failure diff from cr-jail-8 (454 bytes, text/plain)
2011-05-26 19:19 PDT, WebKit Commit Bot 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2011-05-26 19:19:16 PDT
Created attachment 95093 [details] Failure diff from cr-jail-8
Alexey Proskuryakov
Comment 2 2011-05-26 23:39:18 PDT
There were recent changes to CORS code.
Adam Barth
Comment 3 2011-05-26 23:51:50 PDT
Let's see if this continues to flake or whether this is just a low-probability failure.
Note You need to log in before you can comment on or make changes to this bug.