Bug 137350

Summary: REGRESSION(r174120): While number of failures is reasonable with 2 processes, test results seem to be inconsistent between runs (Requested by rfong on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: roger_fong
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
ROLLOUT of r174120 none

WebKit Commit Bot
Reported 2014-10-02 11:16:41 PDT
http://trac.webkit.org/changeset/174120 broke the build: While number of failures is reasonable with 2 processes, test results seem to be inconsistent between runs (Requested by rfong 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 r174120 (1.39 KB, patch)
2014-10-02 11:17 PDT, WebKit Commit Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2014-10-02 11:17:00 PDT
Created attachment 239121 [details] ROLLOUT of r174120 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 2014-10-02 12:15:05 PDT
Comment on attachment 239121 [details] ROLLOUT of r174120 Clearing flags on attachment: 239121 Committed r174223: <http://trac.webkit.org/changeset/174223>
WebKit Commit Bot
Comment 3 2014-10-02 12:15:07 PDT
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.