GitLab

On failure, future transport writes should synchronously return. This is
important on Chrome OS and Linux where we have a separate NSS task runner.
If we query the transport each time (in hopes that it will return the error
code) it becomes an asynchronous error and so the state machine keeps pumping
itself in response to the state change. (It alternates between "write pending"
and "write failed".)

Add a test that asserts we do not keep trying to write to the transport in a
loop.

This fixes one of the infinite loops in bug #381160, but not the other.

BUG=381160

Review URL: https://codereview.chromium.org/337823002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278014 0039d316-1c4b-4281-b951-d872f2087c98