Bug 151776

Summary: REGRESSION(r192955): A large number of the tests added with this change are failing on Windows (Requested by ryanhaddad on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: cavalcantii, simon.fraser
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 99922    
Attachments:
Description Flags
ROLLOUT of r192955 none

WebKit Commit Bot
Reported 2015-12-02 14:50:28 PST
http://trac.webkit.org/changeset/192955 broke the build: A large number of the tests added with this change are failing on Windows (Requested by ryanhaddad on #webkit). This is an automatic bug report generated by webkitbot. If this bug report was created because of a flaky test, please file a bug for the flaky test (if we don't already have one on file) and dup this bug against that bug so that we can track how often these flaky tests fail.
Attachments
ROLLOUT of r192955 (77.72 KB, patch)
2015-12-02 14:50 PST, WebKit Commit Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2015-12-02 14:50:59 PST
Created attachment 266473 [details] ROLLOUT of r192955 Any committer can land this patch automatically by marking it commit-queue+. The commit-queue will build and test the patch before landing to ensure that the rollout will be successful. This process takes approximately 15 minutes. If you would like to land the rollout faster, you can use the following command: webkit-patch land-attachment ATTACHMENT_ID where ATTACHMENT_ID is the ID of this attachment.
WebKit Commit Bot
Comment 2 2015-12-02 14:53:09 PST
Comment on attachment 266473 [details] ROLLOUT of r192955 Clearing flags on attachment: 266473 Committed r192970: <http://trac.webkit.org/changeset/192970>
WebKit Commit Bot
Comment 3 2015-12-02 14:53:12 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.