Revert of Fix computation of runtime for throttled tasks

Revert of Fix computation of runtime for throttled tasks (patchset #3 id:40001 of https://codereview.chromium.org/1718233002/ )

Reason for revert:
Speculative revert for Compile failure on Win, Mac & Precise 64 Beta Bots (crbug.com/590286)

Original issue's description:
> Fix computation of runtime for throttled tasks
>
> The computation of the delayed task runtime was computing the (virtual)
> TimeDomain's now + delay.  That doesn't take into account the skew
> between the real time and the virtual time, which meant timers could
> run sooner than expected for background tabs.  Timers associated with
> foreground tabs are unaffected.
>
> This patch makes the computation of delayed runtime  the responsibility
> of the TimeDomain and introduces a ThrottledTimeDomain which computes
> the delayed runtime as realtime + delay.
>
> This means timers will no longer run sooner than expected.  Under normal
> circumstancs this only timers whose delay modulo 1000ms is less than 100
> ms are less likely to be affected.  Timers whose whose delay modulo
> 1000ms is greater than 900 are highly likely to be affected (there's a
> good chance their delay was too small before).
>
> BUG=587074
>
> Committed: https://crrev.com/b56bbe4ce3e7276a130a00d83cf00e5672cd6be1
> Cr-Commit-Position: refs/heads/master@{#376993}

TBR=skyostil@chromium.org,alexclarke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=587074
Committed: https://crrev.com/7a1d629da81d8218afbf86eb4ff6c977970cd8d4
Cr-Commit-Position: refs/heads/master@{#377995}

[jaydasika, 2016-02-26 20:02:56]

Created Revert of Fix computation of runtime for throttled tasks

[commit-bot: I haz the power, 2016-02-26 20:12:12]

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

[commit-bot: I haz the power, 2016-02-26 20:33:26]

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

[commit-bot: I haz the power, 2016-02-26 20:35:33]

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

[commit-bot: I haz the power, 2016-02-26 20:35:34]

Try jobs failed on following builders:
  chromeos_daisy_chromium_compile_only_ng on tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
  linux_chromium_chromeos_ozone_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  win_chromium_compile_dbg_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)
  win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[jaydasika, 2016-02-26 20:59:22]

The CQ bit was checked by jaydasika@chromium.org

[commit-bot: I haz the power, 2016-02-26 21:00:19]

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

[commit-bot: I haz the power, 2016-02-26 22:07:45]

Committed patchset #2 (id:240001)

[commit-bot: I haz the power, 2016-02-26 22:08:57]

Description was changed from

==========
Revert of Fix computation of runtime for throttled tasks (patchset #3 id:40001
of https://codereview.chromium.org/1718233002/ )

Reason for revert:
Speculative revert for Compile failure on Win, Mac & Precise 64 Beta Bots
(crbug.com/590286) 

Original issue's description:
> Fix computation of runtime for throttled tasks
> 
> The computation of the delayed task runtime was computing the (virtual)
> TimeDomain's now + delay.  That doesn't take into account the skew
> between the real time and the virtual time, which meant timers could
> run sooner than expected for background tabs.  Timers associated with
> foreground tabs are unaffected.
> 
> This patch makes the computation of delayed runtime  the responsibility
> of the TimeDomain and introduces a ThrottledTimeDomain which computes
> the delayed runtime as realtime + delay.
> 
> This means timers will no longer run sooner than expected.  Under normal
> circumstancs this only timers whose delay modulo 1000ms is less than 100
> ms are less likely to be affected.  Timers whose whose delay modulo
> 1000ms is greater than 900 are highly likely to be affected (there's a
> good chance their delay was too small before).
> 
> BUG=587074
> 
> Committed: https://crrev.com/b56bbe4ce3e7276a130a00d83cf00e5672cd6be1
> Cr-Commit-Position: refs/heads/master@{#376993}

TBR=skyostil@chromium.org,alexclarke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=587074
==========

to

==========
Revert of Fix computation of runtime for throttled tasks (patchset #3 id:40001
of https://codereview.chromium.org/1718233002/ )

Reason for revert:
Speculative revert for Compile failure on Win, Mac & Precise 64 Beta Bots
(crbug.com/590286)

Original issue's description:
> Fix computation of runtime for throttled tasks
>
> The computation of the delayed task runtime was computing the (virtual)
> TimeDomain's now + delay.  That doesn't take into account the skew
> between the real time and the virtual time, which meant timers could
> run sooner than expected for background tabs.  Timers associated with
> foreground tabs are unaffected.
>
> This patch makes the computation of delayed runtime  the responsibility
> of the TimeDomain and introduces a ThrottledTimeDomain which computes
> the delayed runtime as realtime + delay.
>
> This means timers will no longer run sooner than expected.  Under normal
> circumstancs this only timers whose delay modulo 1000ms is less than 100
> ms are less likely to be affected.  Timers whose whose delay modulo
> 1000ms is greater than 900 are highly likely to be affected (there's a
> good chance their delay was too small before).
>
> BUG=587074
>
> Committed: https://crrev.com/b56bbe4ce3e7276a130a00d83cf00e5672cd6be1
> Cr-Commit-Position: refs/heads/master@{#376993}

TBR=skyostil@chromium.org,alexclarke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=587074

Committed: https://crrev.com/7a1d629da81d8218afbf86eb4ff6c977970cd8d4
Cr-Commit-Position: refs/heads/master@{#377995}
==========

[commit-bot: I haz the power, 2016-02-26 22:08:58]

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

[jaydasika, 2016-02-26 23:34:41]

A revert of this CL (patchset #2 id:240001) has been created in
https://codereview.chromium.org/1727273008/ by jaydasika@chromium.org.

The reason for reverting is: I reverted the wrong CL. Should have reverted the
cherry-picked CL. So, re-reverting this one..