Add test for action_runner.BeginInteraction and action_runner.EndInteraction.

Add test for action_runner.BeginInteraction and action_runner.EndInteraction.

BUG=368767
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=272549

[nednguyen, 2014-05-21 01:37:15]

I believe this will catch the race condition. I will check this against oilpan
build with caseq change soon.

[tonyg, 2014-05-21 07:03:34]

lgtm

Thanks!

[commit-bot: I haz the power, 2014-05-21 07:05:51]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/nednguyen@google.com/294943006/1

[nednguyen, 2014-05-21 17:52:39]

The CQ bit was unchecked by nednguyen@google.com

[nednguyen, 2014-05-21 17:53:36]

On 2014/05/21 17:52:39, nednguyen wrote:
> The CQ bit was unchecked by mailto:nednguyen@google.com

Try this test with oilpan build with caseq's change today and it doesn't catch
the race condition. I will try to see what else we can do to trigger it.

[nednguyen, 2014-05-22 16:45:28]

On 2014/05/21 17:53:36, nednguyen wrote:
> On 2014/05/21 17:52:39, nednguyen wrote:
> > The CQ bit was unchecked by mailto:nednguyen@google.com
> 
> Try this test with oilpan build with caseq's change today and it doesn't catch
> the race condition. I will try to see what else we can do to trigger it.

Also tried balls_css_keyframe_animations_composited_transform.html which is much
more complicated than blank.html and collect all tracing categories but still
can't trigger the rate condition with this test. I feel like the more
complicated the page is, the more time it would take for start tracing to
actually finish on chrome side, but not sure. This patch would need to be
checked in anyway, but I am not sure whether I should try more complicated page?

[nednguyen, 2014-05-23 16:51:22]

On 2014/05/22 16:45:28, nednguyen wrote:
> On 2014/05/21 17:53:36, nednguyen wrote:
> > On 2014/05/21 17:52:39, nednguyen wrote:
> > > The CQ bit was unchecked by mailto:nednguyen@google.com
> > 
> > Try this test with oilpan build with caseq's change today and it doesn't
catch
> > the race condition. I will try to see what else we can do to trigger it.
> 
> Also tried balls_css_keyframe_animations_composited_transform.html which is
much
> more complicated than blank.html and collect all tracing categories but still
> can't trigger the rate condition with this test. I feel like the more
> complicated the page is, the more time it would take for start tracing to
> actually finish on chrome side, but not sure. This patch would need to be
> checked in anyway, but I am not sure whether I should try more complicated
page?

Actually, I think the test to catch bug/368767 should be about checking whether
inspector handles the start tracing call synchronously. So it should be on the
chrome side. I don't think we need to try too hard to catch that bug on
telemetry unittest side.

[nednguyen, 2014-05-23 16:51:26]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2014-05-23 16:52:47]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/nednguyen@google.com/294943006/1

[commit-bot: I haz the power, 2014-05-23 16:54:45]

Change committed as 272549