Update V8 to version 5.8.111.

Update V8 to version 5.8.111.

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/5dd3abff..6ea247d1

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogelheim@chromium.org

Review-Url: https://codereview.chromium.org/2670973002
Cr-Commit-Position: refs/heads/master@{#447980}
Committed: https://chromium.googlesource.com/chromium/src/+/49e97227eb3b54d9721c27a37a162dc84355d13f

[v8-autoroll, 2017-02-03 09:02:08]

The CQ bit was checked by v8-autoroll@chromium.org

[commit-bot: I haz the power, 2017-02-03 09:02:26]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-03 12:09:00]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1486112528966250, "parent_rev":
"5621cb109071401fc3cc9fc93e70955df0b7ae12", "commit_rev":
"49e97227eb3b54d9721c27a37a162dc84355d13f"}

[commit-bot: I haz the power, 2017-02-03 12:09:32]

Description was changed from

==========
Update V8 to version 5.8.111.

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/5dd3abff..6ea247d1

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogel...
==========

to

==========
Update V8 to version 5.8.111.

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/5dd3abff..6ea247d1

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogel...

Review-Url: https://codereview.chromium.org/2670973002
Cr-Commit-Position: refs/heads/master@{#447980}
Committed:
https://chromium.googlesource.com/chromium/src/+/49e97227eb3b54d9721c27a37a16...
==========

[commit-bot: I haz the power, 2017-02-03 12:09:33]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/49e97227eb3b54d9721c27a37a16...

[joedow, 2017-02-03 20:11:28]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2673953002/ by joedow@chromium.org.

The reason for reverting is: CL Suspected of causing webkit failures in Chromium
trybots:
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linu...

Test (fails due to leak):
inspector/sources/debugger-step/debugger-step-into-custom-element-callbacks.html.

[Michael Achenbach, 2017-02-04 11:56:51]

CC kozyatinskiy, yangguo to help figuring our which inspector CL caused the
leaks. Range:
https://chromium.googlesource.com/v8/v8/+log/5dd3abff..6ea247d1

[Michael Achenbach, 2017-02-04 12:06:52]

@joedow: Is it practice to revert rolls because of non-CQ bots? Maybe my
knowledge is out-of-date - wasn't a sheriff myself in a while...

Please consider landing a layouttest expectation for the one leaking test
instead of reverting the work of several dozens of people. The webkit bot in
question is not part of the CQ. It's also only backed by one slave, so we can't
just add it to our auto-roller...

[kozy, 2017-02-04 17:08:43]

On 2017/02/04 11:56:51, Michael Achenbach wrote:
> CC kozyatinskiy, yangguo to help figuring our which inspector CL caused the
> leaks. Range:
> https://chromium.googlesource.com/v8/v8/+log/5dd3abff..6ea247d1

I can reproduce it locally and am bisecting it right now.

[kozy, 2017-02-04 17:31:54]

On 2017/02/04 17:08:43, kozy wrote:
> On 2017/02/04 11:56:51, Michael Achenbach wrote:
> > CC kozyatinskiy, yangguo to help figuring our which inspector CL caused the
> > leaks. Range:
> > https://chromium.googlesource.com/v8/v8/+log/5dd3abff..6ea247d1
> 
> I can reproduce it locally and am bisecting it right now.

Surprisingly, bisect points to https://codereview.chromium.org/2650193002. Local
revert helped with resolving leak.

[Michael Achenbach, 2017-02-06 08:01:27]

On 2017/02/04 17:31:54, kozy wrote:
> On 2017/02/04 17:08:43, kozy wrote:
> > On 2017/02/04 11:56:51, Michael Achenbach wrote:
> > > CC kozyatinskiy, yangguo to help figuring our which inspector CL caused
the
> > > leaks. Range:
> > > https://chromium.googlesource.com/v8/v8/+log/5dd3abff..6ea247d1
> > 
> > I can reproduce it locally and am bisecting it right now.
> 
> Surprisingly, bisect points to https://codereview.chromium.org/2650193002.
Local
> revert helped with resolving leak.

Thanks a lot for the anaysis! We'll backmerge the revert and try rolling again.

[joedow, 2017-02-06 17:05:35]

joedow@chromium.org changed reviewers:
+ joedow@chromium.org

[joedow, 2017-02-06 17:05:36]

machenbach@, I was going to add an entry into LeakExpectations here:
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/LeakExpec....

However the text in the file said to revert the CL instead of adding an
override.  I interpreted that reverting the auto-roll until the issue was fixed.
 I can add an exception next time if that is preferred.

Joe

[Michael Achenbach, 2017-02-06 18:21:49]

On 2017/02/06 17:05:36, joedow wrote:
> machenbach@, I was going to add an entry into LeakExpectations here:
>
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/LeakExpec....
> 
> However the text in the file said to revert the CL instead of adding an
> override.  I interpreted that reverting the auto-roll until the issue was
fixed.
>  I can add an exception next time if that is preferred.
> 
> Joe

Fair enough. Next time, probably somebody else is sheriff :/

@hablich: lets discuss offline if we can either get the comment in the
expectation file updated for auto-rollers or add the trybot to our additional
trybot list. The latter would require adding some extra slaves to the bot...

Or we wait until next time. This was the first time a layout-test leak hit a V8
roll.