Summary: | REGRESSION(r115594): Caused 10 plus tests crash on Win/Linux debug (Requested by zhenyao on #webkit). | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | WebKit Review Bot <webkit.review.bot> | ||||
Component: | New Bugs | Assignee: | WebKit Review Bot <webkit.review.bot> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | CC: | haraken | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 84908 | ||||||
Attachments: |
|
Description
WebKit Review Bot
2012-04-30 10:46:24 PDT
Created attachment 139474 [details] ROLLOUT of r115594 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. Can you list which tests it caused to crash? Or point to the build where it failed? We expect this assert to get hit since it points out a known bug. So, the right thing is probably to just mark the tests as crashing in debug. (In reply to comment #2) > Can you list which tests it caused to crash? Or point to the build where it failed? We expect this assert to get hit since it points out a known bug. So, the right thing is probably to just mark the tests as crashing in debug. Yes! We want to know it! For the time being, I landed a patch to remove ASSERT() from the code to avoid the crashes. |