Revert "cc: Make scheduler run incoming frame after previous deadline."

Revert "cc: Make scheduler run incoming frame after previous deadline."

This reverts commit d920c93c9c963460b835d19ca4540fe86640b19f.
(Reupload from https://chromium-review.googlesource.com/c/482780/
due to merge conflicts during rebase.)

Reason for revert:

Seems to have caused test failures:
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg_/9549/layout-test-results/fast/events/pointerevents/pointer-event-consumed-touchstart-in-slop-region-actual.txt
and
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg_/9549/layout-test-results/fast/spatial-navigation/snav-z-index-pretty-diff.html

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Win7%20%28dbg%29/builds/9549

Original change's description:
> cc: Make scheduler run incoming frame after previous deadline.
>
> When removing retro frames I made the incoming frame run the previous
> frame's deadline synchronously. This is believed to have regressed
> Event.Latency.OS.TOUCH_MOVED UMA metric. This CL changes the scheduler
> to queue the incoming frame and post a task for it after the previous
> deadline runs. This is a speculative fix for the UMA regression.
>
> R=​enne
> BUG=702372
>
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Change-Id: I0d8b0a5df90186b2158e4249540929b9b5ecc70b
> Reviewed-on: https://chromium-review.googlesource.com/478852
> Reviewed-by: enne <enne@chromium.org>;
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>;
> Cr-Commit-Position: refs/heads/master@{#465769}

TBR=enne@chromium.org,sunnyps@chromium.org,chromium-reviews@chromium.org,cc-bugs@chromium.org,scheduler-bugs@chromium.org
# Not skipping any steps as this is a manual revert.
BUG=702372
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2832503005
Cr-Commit-Position: refs/heads/master@{#465972}
Committed: https://chromium.googlesource.com/chromium/src/+/95f34789951a95ea306db1b8e9b568696a3cacaa

[fhorschig, 2017-04-20 09:10:39]

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

[commit-bot: I haz the power, 2017-04-20 09:11:06]

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

[fhorschig, 2017-04-20 09:11:57]

Description was changed from

==========
Revert "cc: Make scheduler run incoming frame after previous deadline."

This reverts commit d920c93c9c963460b835d19ca4540fe86640b19f.
(Reupload from https://chromium-review.googlesource.com/c/482780/
due to merge conflicts during rebase.)

Reason for revert:

Seems to have caused test failures:
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...
and
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Win7...

Original change's description:
> cc: Make scheduler run incoming frame after previous deadline.
>
> When removing retro frames I made the incoming frame run the previous
> frame's deadline synchronously. This is believed to have regressed
> Event.Latency.OS.TOUCH_MOVED UMA metric. This CL changes the scheduler
> to queue the incoming frame and post a task for it after the previous
> deadline runs. This is a speculative fix for the UMA regression.
>
> R=​enne
> BUG=702372
>
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Change-Id: I0d8b0a5df90186b2158e4249540929b9b5ecc70b
> Reviewed-on: https://chromium-review.googlesource.com/478852
> Reviewed-by: enne <enne@chromium.org>
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#465769}

TBR=enne@chromium.org,sunnyps@chromium.org,chromium-reviews@chromium.org,cc-b...
BUG=702372
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

to

==========
Revert "cc: Make scheduler run incoming frame after previous deadline."

This reverts commit d920c93c9c963460b835d19ca4540fe86640b19f.
(Reupload from https://chromium-review.googlesource.com/c/482780/
due to merge conflicts during rebase.)

Reason for revert:

Seems to have caused test failures:
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...
and
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Win7...

Original change's description:
> cc: Make scheduler run incoming frame after previous deadline.
>
> When removing retro frames I made the incoming frame run the previous
> frame's deadline synchronously. This is believed to have regressed
> Event.Latency.OS.TOUCH_MOVED UMA metric. This CL changes the scheduler
> to queue the incoming frame and post a task for it after the previous
> deadline runs. This is a speculative fix for the UMA regression.
>
> R=​enne
> BUG=702372
>
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Change-Id: I0d8b0a5df90186b2158e4249540929b9b5ecc70b
> Reviewed-on: https://chromium-review.googlesource.com/478852
> Reviewed-by: enne <enne@chromium.org>
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#465769}

TBR=enne@chromium.org,sunnyps@chromium.org,chromium-reviews@chromium.org,cc-b...
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=702372
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

[commit-bot: I haz the power, 2017-04-20 09:32:09]

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

[commit-bot: I haz the power, 2017-04-20 09:32:09]

Dry run: This issue passed the CQ dry run.

[fhorschig, 2017-04-20 10:01:29]

Description was changed from

==========
Revert "cc: Make scheduler run incoming frame after previous deadline."

This reverts commit d920c93c9c963460b835d19ca4540fe86640b19f.
(Reupload from https://chromium-review.googlesource.com/c/482780/
due to merge conflicts during rebase.)

Reason for revert:

Seems to have caused test failures:
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...
and
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Win7...

Original change's description:
> cc: Make scheduler run incoming frame after previous deadline.
>
> When removing retro frames I made the incoming frame run the previous
> frame's deadline synchronously. This is believed to have regressed
> Event.Latency.OS.TOUCH_MOVED UMA metric. This CL changes the scheduler
> to queue the incoming frame and post a task for it after the previous
> deadline runs. This is a speculative fix for the UMA regression.
>
> R=​enne
> BUG=702372
>
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Change-Id: I0d8b0a5df90186b2158e4249540929b9b5ecc70b
> Reviewed-on: https://chromium-review.googlesource.com/478852
> Reviewed-by: enne <enne@chromium.org>
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#465769}

TBR=enne@chromium.org,sunnyps@chromium.org,chromium-reviews@chromium.org,cc-b...
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=702372
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

to

==========
Revert "cc: Make scheduler run incoming frame after previous deadline."

This reverts commit d920c93c9c963460b835d19ca4540fe86640b19f.
(Reupload from https://chromium-review.googlesource.com/c/482780/
due to merge conflicts during rebase.)

Reason for revert:

Seems to have caused test failures:
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...
and
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Win7...

Original change's description:
> cc: Make scheduler run incoming frame after previous deadline.
>
> When removing retro frames I made the incoming frame run the previous
> frame's deadline synchronously. This is believed to have regressed
> Event.Latency.OS.TOUCH_MOVED UMA metric. This CL changes the scheduler
> to queue the incoming frame and post a task for it after the previous
> deadline runs. This is a speculative fix for the UMA regression.
>
> R=​enne
> BUG=702372
>
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Change-Id: I0d8b0a5df90186b2158e4249540929b9b5ecc70b
> Reviewed-on: https://chromium-review.googlesource.com/478852
> Reviewed-by: enne <enne@chromium.org>
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#465769}

TBR=enne@chromium.org,sunnyps@chromium.org,chromium-reviews@chromium.org,cc-b...
# Not skipping any steps as this is a manual revert.
BUG=702372
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

[fhorschig, 2017-04-20 11:14:31]

The CQ bit was checked by fhorschig@chromium.org

[commit-bot: I haz the power, 2017-04-20 11:14:40]

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-04-20 11:19:32]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492686871614830, "parent_rev":
"aa89ede3945ca91f2c12500c213a4d08f8b29886", "commit_rev":
"95f34789951a95ea306db1b8e9b568696a3cacaa"}

[commit-bot: I haz the power, 2017-04-20 11:19:43]

Description was changed from

==========
Revert "cc: Make scheduler run incoming frame after previous deadline."

This reverts commit d920c93c9c963460b835d19ca4540fe86640b19f.
(Reupload from https://chromium-review.googlesource.com/c/482780/
due to merge conflicts during rebase.)

Reason for revert:

Seems to have caused test failures:
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...
and
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Win7...

Original change's description:
> cc: Make scheduler run incoming frame after previous deadline.
>
> When removing retro frames I made the incoming frame run the previous
> frame's deadline synchronously. This is believed to have regressed
> Event.Latency.OS.TOUCH_MOVED UMA metric. This CL changes the scheduler
> to queue the incoming frame and post a task for it after the previous
> deadline runs. This is a speculative fix for the UMA regression.
>
> R=​enne
> BUG=702372
>
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Change-Id: I0d8b0a5df90186b2158e4249540929b9b5ecc70b
> Reviewed-on: https://chromium-review.googlesource.com/478852
> Reviewed-by: enne <enne@chromium.org>
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#465769}

TBR=enne@chromium.org,sunnyps@chromium.org,chromium-reviews@chromium.org,cc-b...
# Not skipping any steps as this is a manual revert.
BUG=702372
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

to

==========
Revert "cc: Make scheduler run incoming frame after previous deadline."

This reverts commit d920c93c9c963460b835d19ca4540fe86640b19f.
(Reupload from https://chromium-review.googlesource.com/c/482780/
due to merge conflicts during rebase.)

Reason for revert:

Seems to have caused test failures:
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...
and
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7__dbg...

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Win7...

Original change's description:
> cc: Make scheduler run incoming frame after previous deadline.
>
> When removing retro frames I made the incoming frame run the previous
> frame's deadline synchronously. This is believed to have regressed
> Event.Latency.OS.TOUCH_MOVED UMA metric. This CL changes the scheduler
> to queue the incoming frame and post a task for it after the previous
> deadline runs. This is a speculative fix for the UMA regression.
>
> R=​enne
> BUG=702372
>
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Change-Id: I0d8b0a5df90186b2158e4249540929b9b5ecc70b
> Reviewed-on: https://chromium-review.googlesource.com/478852
> Reviewed-by: enne <enne@chromium.org>
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#465769}

TBR=enne@chromium.org,sunnyps@chromium.org,chromium-reviews@chromium.org,cc-b...
# Not skipping any steps as this is a manual revert.
BUG=702372
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2832503005
Cr-Commit-Position: refs/heads/master@{#465972}
Committed:
https://chromium.googlesource.com/chromium/src/+/95f34789951a95ea306db1b8e9b5...
==========

[commit-bot: I haz the power, 2017-04-20 11:19:44]

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

[sunnyps, 2017-04-20 20:46:33]

On 2017/04/20 11:19:44, commit-bot: I haz the power wrote:
> Committed patchset #1 (id:1) as
>
https://chromium.googlesource.com/chromium/src/+/95f34789951a95ea306db1b8e9b5...

Those tests are still failing btw.

[sunnyps, 2017-04-20 20:51:01]

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

The reason for reverting is: Didn't cause the test failures (see
crbug.com/713740).