http://trac.webkit.org/changeset/80458 broke the build:
caused tests to crash on several chromium bots (Requested by ukai 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
Created attachment 84927 [details]
ROLLOUT of r80458
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 on attachment 84927 [details]
ROLLOUT of r80458
Clearing flags on attachment: 84927
Committed r80461: <http://trac.webkit.org/changeset/80461>
All reviewed patches have been landed. Closing bug.
http://trac.webkit.org/changeset/80461 might have broken GTK Linux 32-bit Release
If you could, it would be helpful if you re-open the original bug when rolling something out.
Thanks for handling this breakage Ukai!
(In reply to comment #6)
> If you could, it would be helpful if you re-open the original bug when rolling something out.
Ah, I should have done that.
Ideally the commit-queue should know how to do it when landing rollout patches, but it's not that smart yet. :)
It probably could be taught to do so by just checking self._patch.is_rollout() in:
and telling self._delegate to reopen the bug.