http://trac.webkit.org/changeset/134144 broke the build:
seems to break win 7 chromium browser test (Requested by hayato 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 173531 [details]
ROLLOUT of r134144
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.
r134144 seems to break Win7 chromium browser tests.
The following tests started to fail since http://build.chromium.org/p/chromium.webkit/builders/Win7%20%28dbg%29/builds/8232.
[3960:884:1110/054331:20249600:INFO:CONSOLE(0)] "Only unpacked extensions and apps installed from the Chrome Web Store can load NaCl modules without enabling Native Client in about:flags.", source: (0)
[3960:884:1110/054332:20249912:FATAL:webcursor_win.cc(104)] Check failed: false.
Check failed in wecursor_win.cc:104.
r134144 seems to be related. Let me rollout that and watch the result.
Comment on attachment 173531 [details]
ROLLOUT of r134144
Clearing flags on attachment: 173531
Committed r134183: <http://trac.webkit.org/changeset/134183>
All reviewed patches have been landed. Closing bug.
Really? I thought that patch just added some tests...
(In reply to comment #5)
> Really? I thought that patch just added some tests...
I am pretty sure the problem is with the builder.
For the record this was indeed my fault (one tiny line added to the product itself to support the tests, and I missed adding braces). See bug 100550 for details and improvements to make it harder to hit this specific issue in the future. Sorry for the trouble.