Bug 38007 – REGRESSION(r58110): Caused an internal compiler error on Qt (Requested by abarth on #webkit).

• Component: New Bugs
• Status: RESOLVED FIXED

[WebKit Review Bot]

http://trac.webkit.org/changeset/58110 broke the build:
Caused an internal compiler error on Qt (Requested by abarth 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

[WebKit Review Bot]

Created attachment 54095 [details]
ROLLOUT of r58110

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.

[Adam Barth]

Comment on attachment 54095 [details]
ROLLOUT of r58110

go go gadget commit queue

[Adam Barth]

http://build.webkit.org/builders/Qt%20Windows%2032-bit%20Release/builds/459/steps/compile-webkit/logs/stdio

[Steve Block]

I admit that the waterfall makes it look like my change is at fault, but it seems hard to believe. All my change does is remove an OS(ANDROID) guard. Plus it built fine on the Qt try bot (see Bug 37948).

Is there a Qt developer I can contact to see if they can reproduce the build problem locally?

[WebKit Commit Bot]

Comment on attachment 54095 [details]
ROLLOUT of r58110

Clearing flags on attachment: 54095

Committed r58118: <http://trac.webkit.org/changeset/58118>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Adam Barth]

> Is there a Qt developer I can contact to see if they can reproduce the build
> problem locally?

I wouldn't stress too much about it.  If the error is still there after the rollout, we can blame the bot and roll your patch back in.

[Steve Block]

My change has now been rolled out but the Qt build still fails in the same way (http://build.webkit.org/builders/Qt%20Windows%2032-bit%20Release/builds/461)

Adam, are you happy for me to put the change back in?

[Adam Barth]

> Adam, are you happy for me to put the change back in?

Yep!  Thanks for you patience.  You can either land it yourself or we can have the bot take care of it.