Bug 45096 - REGRESSION(r66622): Caused Snow Leopard failures (Requested by eseidel2 on #webkit).
Summary: REGRESSION(r66622): Caused Snow Leopard failures (Requested by eseidel2 on #w...
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other OS X 10.5
: P2 Normal
Assignee: WebKit Review Bot
Depends on:
Blocks: 45013
  Show dependency treegraph
Reported: 2010-09-02 02:25 PDT by WebKit Review Bot
Modified: 2010-09-02 02:31 PDT (History)
3 users (show)

See Also:

ROLLOUT of r66622 (13.63 KB, patch)
2010-09-02 02:25 PDT, WebKit Review Bot
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description WebKit Review Bot 2010-09-02 02:25:23 PDT
http://trac.webkit.org/changeset/66622 broke the build:
Caused Snow Leopard failures (Requested by eseidel2 on #webkit).

This is an automatic bug report generated by the sheriff-bot. 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 case pain.

"Only you can prevent forest fires." -- Smokey the Bear
Comment 1 WebKit Review Bot 2010-09-02 02:25:40 PDT
Created attachment 66341 [details]
ROLLOUT of r66622

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 --ignore-builders

where ATTACHMENT_ID is the ID of this attachment.
Comment 2 Eric Seidel (no email) 2010-09-02 02:26:29 PDT
Comment on attachment 66341 [details]
ROLLOUT of r66622

This appears to have been failing ever since it landed (10 hours ago).
Comment 3 Eric Seidel (no email) 2010-09-02 02:28:32 PDT
Looks like there is a fix posted on the original bug.  Investigating.
Comment 4 Eric Seidel (no email) 2010-09-02 02:31:24 PDT
Landing the fix from Jer Noble instead of a rollout.  Thanks Jer!