[XHR] Fix interactive-state.html layout test for the new ProgressEvent throttling algorithm

[XHR] Fix interactive-state.html layout test for the new ProgressEvent throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
R=yhirano

Committed: https://crrev.com/30508d30a3ae392ecfb611ba42e2128e225c3c6a
Cr-Commit-Position: refs/heads/master@{#362123}

[tyoshino (SeeGerritForStatus), 2015-11-30 12:14:33]

Description was changed from

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
==========

to

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
==========

[tyoshino (SeeGerritForStatus), 2015-11-30 12:14:33]

tyoshino@chromium.org changed reviewers:
+ yhirano@chromium.org

[yhirano, 2015-11-30 12:19:36]

On 2015/11/30 12:14:39, tyoshino wrote:

Is 0.2sec sufficient?

[tyoshino (SeeGerritForStatus), 2015-11-30 12:22:57]

On 2015/11/30 12:19:36, yhirano wrote:
> On 2015/11/30 12:14:39, tyoshino wrote:
> 
> Is 0.2sec sufficient?

For non-Oilpan debug run on my workstation, even 0.1 sec seems to be sufficient.
For heavier builds, not sure. How about 0.5?

[tyoshino (SeeGerritForStatus), 2015-11-30 12:23:46]

On 2015/11/30 12:22:57, tyoshino wrote:
> On 2015/11/30 12:19:36, yhirano wrote:
> > On 2015/11/30 12:14:39, tyoshino wrote:
> > 
> > Is 0.2sec sufficient?
> 
> For non-Oilpan debug run on my workstation, even 0.1 sec seems to be
sufficient.
> For heavier builds, not sure. How about 0.5?

Sorry. Please ignore "non-Oilpan".

[tyoshino (SeeGerritForStatus), 2015-11-30 12:36:02]

On 2015/11/30 12:23:46, tyoshino wrote:
> On 2015/11/30 12:22:57, tyoshino wrote:
> > On 2015/11/30 12:19:36, yhirano wrote:
> > > On 2015/11/30 12:14:39, tyoshino wrote:
> > > 
> > > Is 0.2sec sufficient?
> > 
> > For non-Oilpan debug run on my workstation, even 0.1 sec seems to be
> sufficient.
> > For heavier builds, not sure. How about 0.5?
> 
> Sorry. Please ignore "non-Oilpan".

Discussed offline and updated the sleep time to 1 sec

[yhirano, 2015-11-30 12:36:55]

On 2015/11/30 12:36:02, tyoshino wrote:
> On 2015/11/30 12:23:46, tyoshino wrote:
> > On 2015/11/30 12:22:57, tyoshino wrote:
> > > On 2015/11/30 12:19:36, yhirano wrote:
> > > > On 2015/11/30 12:14:39, tyoshino wrote:
> > > > 
> > > > Is 0.2sec sufficient?
> > > 
> > > For non-Oilpan debug run on my workstation, even 0.1 sec seems to be
> > sufficient.
> > > For heavier builds, not sure. How about 0.5?
> > 
> > Sorry. Please ignore "non-Oilpan".
> 
> Discussed offline and updated the sleep time to 1 sec

Thank you, lgtm

[tyoshino (SeeGerritForStatus), 2015-11-30 12:59:36]

Description was changed from

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
==========

to

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
R=yhirano
==========

[tyoshino (SeeGerritForStatus), 2015-11-30 12:59:40]

The CQ bit was checked by tyoshino@chromium.org

[commit-bot: I haz the power, 2015-11-30 13:00:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1484743002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1484743002/20001

[commit-bot: I haz the power, 2015-11-30 13:43:49]

Description was changed from

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
R=yhirano
==========

to

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
R=yhirano
==========

[commit-bot: I haz the power, 2015-11-30 13:43:49]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-11-30 13:45:03]

Description was changed from

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
R=yhirano
==========

to

==========
[XHR] Fix interactive-state.html layout test for the new ProgressEvent
throttling algorithm

A new ProgressEvent throttling algorithm has been introduced by
https://codereview.chromium.org/1455513002/

The new algorithm suppresses redundant "progress" ProgressEvents using
50 ms slot. Update the interactive-state.html test for the new
algorithm.

BUG=336066
R=yhirano

Committed: https://crrev.com/30508d30a3ae392ecfb611ba42e2128e225c3c6a
Cr-Commit-Position: refs/heads/master@{#362123}
==========

[commit-bot: I haz the power, 2015-11-30 13:45:04]

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