[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc: https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx1k/edit

BUG=646559
Committed: https://crrev.com/0bdb1f395432064cc19799facf055317a12ec6ce
Cr-Commit-Position: refs/heads/master@{#431198}

[nhiroki, 2016-11-09 10:33:03]

Description was changed from

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak on LayoutTests.
This leak was fixed by https://codereview.chromium.org/2482393002/

This reland CL also changes layout tests because the original tests depended on
leaked Document context. After the leak is fixed, the context can be destroyed
earlier than console messages from Worklets are printed. New layout tests wait
for console messages

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

to

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak on LayoutTests.
This leak was fixed by https://codereview.chromium.org/2482393002/

This reland CL also changes layout tests because the original tests depended on
leaked Document context. After the leak is fixed, the context can be destroyed
earlier than console messages from Worklets are printed. New layout tests wait
for console messages.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

[nhiroki, 2016-11-10 00:45:38]

The CQ bit was checked by nhiroki@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-10 00:46:24]

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

[nhiroki, 2016-11-10 01:44:49]

The CQ bit was checked by nhiroki@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-10 01:45:15]

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

[nhiroki, 2016-11-10 02:20:00]

Description was changed from

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak on LayoutTests.
This leak was fixed by https://codereview.chromium.org/2482393002/

This reland CL also changes layout tests because the original tests depended on
leaked Document context. After the leak is fixed, the context can be destroyed
earlier than console messages from Worklets are printed. New layout tests wait
for console messages.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

to

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak on LayoutTests.
This leak was fixed by https://codereview.chromium.org/2482393002/

This reland CL also changes layout tests because the original tests depended on
leaked Document context. After the leak is fixed, the context can be destroyed
earlier than console messages from Worklets are printed. New layout tests wait
for console messages.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

[nhiroki, 2016-11-10 02:20:00]

nhiroki@chromium.org changed reviewers:
+ dgozman@chromium.org

[nhiroki, 2016-11-10 02:25:14]

Description was changed from

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak on LayoutTests.
This leak was fixed by https://codereview.chromium.org/2482393002/

This reland CL also changes layout tests because the original tests depended on
leaked Document context. After the leak is fixed, the context can be destroyed
earlier than console messages from Worklets are printed. New layout tests wait
for console messages.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

to

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

[nhiroki, 2016-11-10 02:25:51]

Hi dgozman@, can you take another look at this? I changed layout tests from the
original CL to fix test flakiness. Thanks.

[commit-bot: I haz the power, 2016-11-10 03:50:20]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-10 03:50:21]

Dry run: This issue passed the CQ dry run.

[dgozman, 2016-11-10 06:22:12]

lgtm

[nhiroki, 2016-11-10 06:40:21]

Description was changed from

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

to

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
TBR=haraken@chromium.org
==========

[nhiroki, 2016-11-10 06:40:21]

nhiroki@chromium.org changed reviewers:
+ haraken@chromium.org

[haraken, 2016-11-10 06:41:29]

LGTM

[nhiroki, 2016-11-10 06:41:48]

+haraken@ for WorkerOrWorkletScriptController.cpp.

Let me use TBR because there are no changes in C++ files from the original CL.

[nhiroki, 2016-11-10 06:42:17]

On 2016/11/10 06:41:29, haraken wrote:
> LGTM

Thank you! You're sooooooooooooo fast :D

[nhiroki, 2016-11-10 06:42:41]

Description was changed from

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
TBR=haraken@chromium.org
==========

to

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

[nhiroki, 2016-11-10 06:47:20]

The CQ bit was checked by nhiroki@chromium.org

[commit-bot: I haz the power, 2016-11-10 06:47:35]

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, 2016-11-10 06:52:11]

Description was changed from

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

to

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

[commit-bot: I haz the power, 2016-11-10 06:52:13]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-11-10 06:54:41]

Description was changed from

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559
==========

to

==========
[Reland] DevTools: Make WorkerThreadDebugger available for Worklets

Original CL: https://codereview.chromium.org/2456733002/

The original CL was reverted because there was a memory leak. This leak was
fixed by https://codereview.chromium.org/2482393002/

In addition to that, this reland CL changes layout tests added by the original
CL because they depended on leaked Document context. After the leak is fixed,
the context can be destroyed earlier than console messages from Worklets are
printed. New layout tests wait until console messages are printed.

<Original Description>

DevTools is now disabled on Worklets because worker's debugger infrastructure(*)
cannot host multiple worklet execution contexts on a single thread.
(*) Worklet has been implemented on the worker infrastructure.

To support it, this CL does following things:

- This expands 1:1 relationship between WorkerThreadDebugger and WorkerThread to
  1:M relationship. The debugger has a ID-WorkerThread map to manage multiple
  WorkerThreads. WorkerThread is added when worklet context is created and
  removed when the context is destroyed.

- This decouples lifetime of WorkerThreadDebugger from lifetime of worklet
  context. Before this CL, the debugger has the same lifetime of the context.
  This prevents the debugger from hosting multiple contexts. After this CL,
  the debugger has the same lifetime of WorkerBackingThread, and attaches to
  worklet context when it's created.

DesignDoc:
https://docs.google.com/document/d/1v0dNB6jWMe7w6OeK-Vlnn-Q4qW7KI4m97LGnMefUx...

BUG=646559

Committed: https://crrev.com/0bdb1f395432064cc19799facf055317a12ec6ce
Cr-Commit-Position: refs/heads/master@{#431198}
==========

[commit-bot: I haz the power, 2016-11-10 06:54:42]

Patchset 2 (id:??) landed as
https://crrev.com/0bdb1f395432064cc19799facf055317a12ec6ce
Cr-Commit-Position: refs/heads/master@{#431198}

[hiroshige, 2016-11-11 08:23:21]

On 2016/11/10 06:54:42, commit-bot: I haz the power wrote:
> Patchset 2 (id:??) landed as
> https://crrev.com/0bdb1f395432064cc19799facf055317a12ec6ce
> Cr-Commit-Position: refs/heads/master@{#431198}

The test inspector/console/console-on-animation-worklet.html added by this CL is
quite flaky:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=in...

[nhiroki, 2016-11-11 10:19:30]

On 2016/11/11 08:23:21, hiroshige wrote:
> On 2016/11/10 06:54:42, commit-bot: I haz the power wrote:
> > Patchset 2 (id:??) landed as
> > https://crrev.com/0bdb1f395432064cc19799facf055317a12ec6ce
> > Cr-Commit-Position: refs/heads/master@{#431198}
> 
> The test inspector/console/console-on-animation-worklet.html added by this CL
is
> quite flaky:
>
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=in...

Thank you for reporting this. I'll update TestExpectations...