Revert of [ResourceScheduler] Yield after starting several requests

Revert of [ResourceScheduler] Yield after starting several requests (patchset #9 id:240001 of https://codereview.chromium.org/2682163002/ )

Reason for revert:
Regresses blob requests making them delayable.

Original issue's description:
> [ResourceScheduler] Yield after starting several requests
> 
> This CL periodically yields the ResourceScheduler after starting several
> requests. This gives existing IO tasks (such as active network requests) a
> chance to run between network starts. This should result in less jank and more
> interleaved network request tasks.
> 
> BUG=655585
> 
> Review-Url: https://codereview.chromium.org/2682163002
> Cr-Commit-Position: refs/heads/master@{#449895}
> Committed: https://chromium.googlesource.com/chromium/src/+/1a8d5f3805dbae5242cf7dce14df3807344dae37

TBR=csharrison@chromium.org,isherman@chromium.org,jkarlin@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=655585
Review-Url: https://codereview.chromium.org/2708323002
Cr-Commit-Position: refs/heads/master@{#451946}
Committed: https://chromium.googlesource.com/chromium/src/+/a9757ebf44c92e009d075322ad35f008b0bfa1ad

[mtomasz, 2017-02-22 03:52:52]

Created Revert of [ResourceScheduler] Yield after starting several requests

[mtomasz, 2017-02-22 03:53:38]

This CL broke FSP API tests. It was incorrectly assumed that the FSP API tests
were racy, but they actually caught the regression.

[mtomasz, 2017-02-22 03:53:53]

The CQ bit was checked by mtomasz@chromium.org

[mtomasz, 2017-02-22 03:53:54]

The CQ bit was unchecked by mtomasz@chromium.org

[mtomasz, 2017-02-22 03:54:41]

The CQ bit was checked by mtomasz@chromium.org

[mtomasz, 2017-02-22 03:55:01]

Reverting, as this CL may break user files.

[commit-bot: I haz the power, 2017-02-22 03:56:01]

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

[Charlie Harrison, 2017-02-22 04:39:08]

Hey mtomasz,
Can you point to a bug or resource showing the failure and why this is a true
regression? We should land a test that will fail reproducibly with this.

[Charlie Harrison, 2017-02-22 04:39:52]

Oops, just noticed you posted this information on the original CL :) sorry for
the noise.

[commit-bot: I haz the power, 2017-02-22 07:29:10]

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

[commit-bot: I haz the power, 2017-02-22 07:29:11]

Try jobs failed on following builders:
  linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[mtomasz, 2017-02-22 07:31:36]

The CQ bit was checked by mtomasz@chromium.org

[commit-bot: I haz the power, 2017-02-22 07:33:22]

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-02-22 09:09:28]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487748696225420, "parent_rev":
"0310d37ba38d61b22c62a8abcf2c0aea0bc6b44d", "commit_rev":
"a9757ebf44c92e009d075322ad35f008b0bfa1ad"}

[commit-bot: I haz the power, 2017-02-22 09:10:05]

Description was changed from

==========
Revert of [ResourceScheduler] Yield after starting several requests (patchset #9
id:240001 of https://codereview.chromium.org/2682163002/ )

Reason for revert:
Regresses blob requests making them delayable.

Original issue's description:
> [ResourceScheduler] Yield after starting several requests
> 
> This CL periodically yields the ResourceScheduler after starting several
> requests. This gives existing IO tasks (such as active network requests) a
> chance to run between network starts. This should result in less jank and more
> interleaved network request tasks.
> 
> BUG=655585
> 
> Review-Url: https://codereview.chromium.org/2682163002
> Cr-Commit-Position: refs/heads/master@{#449895}
> Committed:
https://chromium.googlesource.com/chromium/src/+/1a8d5f3805dbae5242cf7dce14df...

TBR=csharrison@chromium.org,isherman@chromium.org,jkarlin@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=655585
==========

to

==========
Revert of [ResourceScheduler] Yield after starting several requests (patchset #9
id:240001 of https://codereview.chromium.org/2682163002/ )

Reason for revert:
Regresses blob requests making them delayable.

Original issue's description:
> [ResourceScheduler] Yield after starting several requests
> 
> This CL periodically yields the ResourceScheduler after starting several
> requests. This gives existing IO tasks (such as active network requests) a
> chance to run between network starts. This should result in less jank and more
> interleaved network request tasks.
> 
> BUG=655585
> 
> Review-Url: https://codereview.chromium.org/2682163002
> Cr-Commit-Position: refs/heads/master@{#449895}
> Committed:
https://chromium.googlesource.com/chromium/src/+/1a8d5f3805dbae5242cf7dce14df...

TBR=csharrison@chromium.org,isherman@chromium.org,jkarlin@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=655585

Review-Url: https://codereview.chromium.org/2708323002
Cr-Commit-Position: refs/heads/master@{#451946}
Committed:
https://chromium.googlesource.com/chromium/src/+/a9757ebf44c92e009d075322ad35...
==========

[commit-bot: I haz the power, 2017-02-22 09:10:06]

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

[jkarlin, 2017-02-22 14:19:04]

Thanks for pointing out the break in contract, I'll fix it so that non http(s)
requests aren't delayed. However, it's not clear to me that a delay in starting
a request should cause a test to get out-of-order data. That sounds like an
existing problem that this revealed.

[jkarlin, 2017-02-22 15:14:22]

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

The reason for reverting is: Adds a check for http(s) before yielding the
scheduler..