Bug 172785

Summary: REGRESSION(r217611): "caused wasm-hashset-many.html to become flaky." (Requested by keith_miller on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: keith_miller
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 172759, 172775    
Attachments:
Description Flags
ROLLOUT of r217611 none

WebKit Commit Bot
Reported 2017-05-31 16:22:03 PDT
http://trac.webkit.org/changeset/217611 broke the build: "caused wasm-hashset-many.html to become flaky." (Requested by keith_miller 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 r217611 (48.41 KB, patch)
2017-05-31 16:22 PDT, WebKit Commit Bot
no flags
WebKit Commit Bot
Comment 1 2017-05-31 16:22:14 PDT
Created attachment 311652 [details] ROLLOUT of r217611 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 2017-05-31 16:25:08 PDT
Comment on attachment 311652 [details] ROLLOUT of r217611 Clearing flags on attachment: 311652 Committed r217638: <http://trac.webkit.org/changeset/217638>
WebKit Commit Bot
Comment 3 2017-05-31 16:25:09 PDT
All reviewed patches have been landed. Closing bug.
Alexey Proskuryakov
Comment 4 2017-05-31 20:07:12 PDT
*** Bug 172781 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.