Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also adds text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357
Committed: https://crrev.com/09721f55334a28503df6bc51cb10f028ebc9f87f
Cr-Commit-Position: refs/heads/master@{#438756}

[yhirano, 2016-12-13 08:29:59]

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

[commit-bot: I haz the power, 2016-12-13 08:30:18]

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

[yhirano, 2016-12-13 08:33:32]

Description was changed from

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

BUG=669357
==========

to

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also add text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357
==========

[yhirano, 2016-12-13 08:33:53]

Description was changed from

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also add text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357
==========

to

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also adds text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357
==========

[commit-bot: I haz the power, 2016-12-13 10:41:30]

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

[commit-bot: I haz the power, 2016-12-13 10:41:30]

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

[yhirano, 2016-12-13 10:42:57]

yhirano@chromium.org changed reviewers:
+ jam@chromium.org, tzik@chromium.org

[tzik, 2016-12-13 10:50:01]

lgtm

[jam, 2016-12-13 17:19:04]

lgtm

[yhirano, 2016-12-13 17:44:45]

The CQ bit was checked by yhirano@chromium.org

[commit-bot: I haz the power, 2016-12-13 17:45:09]

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, 2016-12-13 20:07:17]

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

[commit-bot: I haz the power, 2016-12-13 20:07:19]

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

[yhirano, 2016-12-15 02:08:06]

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

[commit-bot: I haz the power, 2016-12-15 02:08:16]

Dry run: 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, 2016-12-15 02:14:45]

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

[commit-bot: I haz the power, 2016-12-15 02:14:46]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
  win_clang on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/...)

[yhirano, 2016-12-15 02:20:30]

The CQ bit was checked by yhirano@chromium.org

[yhirano, 2016-12-15 02:20:31]

The patchset sent to the CQ was uploaded after l-g-t-m from jam@chromium.org,
tzik@chromium.org
Link to the patchset: https://codereview.chromium.org/2573743002/#ps20001
(title: "fix")

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

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, 2016-12-15 02:25:55]

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

[commit-bot: I haz the power, 2016-12-15 02:25:56]

Try jobs failed on following builders:
  win_clang on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/...)

[yhirano, 2016-12-15 04:14:01]

The CQ bit was checked by yhirano@chromium.org

[commit-bot: I haz the power, 2016-12-15 04:14:34]

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, 2016-12-15 05:29:18]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1481775241458100,
"parent_rev": "653011ff50ad95f0ba82f2a5a934cf7a92ce613f", "commit_rev":
"fe86952b82e3655cbb7d39cf8dfa4d083f668cd7"}

[commit-bot: I haz the power, 2016-12-15 05:30:10]

Description was changed from

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also adds text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357
==========

to

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also adds text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357

Review-Url: https://codereview.chromium.org/2573743002
==========

[commit-bot: I haz the power, 2016-12-15 05:30:11]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-12-15 05:33:42]

Description was changed from

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also adds text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357

Review-Url: https://codereview.chromium.org/2573743002
==========

to

==========
Handle MOJO_RESULT_BUSY result in URLResponseBodyConsumer

URLResponseBodyConsumer reads data from a mojo data pipe and dispatches it as a
URLResponseBodyConsumer::ReceivedData. When the dispatched data is destructed,
mojo::EndReadDataRaw is called. Until then, mojo::BeginRead will return
MOJO_RESULT_BUSY. This CL implements the correct handling for such a case.

This mis-handling was the cause of the failure of
virtual/mojo-loading/http/tests/inspector/network/network-fetch.html. This CL
also adds text() call in makeFetch function so that the backpressure mechanism
won't stop the loading.

BUG=669357

Committed: https://crrev.com/09721f55334a28503df6bc51cb10f028ebc9f87f
Cr-Commit-Position: refs/heads/master@{#438756}
==========

[commit-bot: I haz the power, 2016-12-15 05:33:43]

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