The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/30943ee5e8e8b775a6870c8ef2fa0a92d56df1d9

commit 30943ee5e8e8b775a6870c8ef2fa0a92d56df1d9
Author: rch <rch@chromium.org>
Date: Mon Jun 12 21:28:44 2017

When a stream is created for a QUIC session to a server which has been
marked as broken, mark the session as going away.

BUG= 731303 

Review-Url: https://codereview.chromium.org/2933773002
Cr-Commit-Position: refs/heads/master@{#478771}

[modify] https://crrev.com/30943ee5e8e8b775a6870c8ef2fa0a92d56df1d9/net/quic/chromium/quic_chromium_client_session.cc
[modify] https://crrev.com/30943ee5e8e8b775a6870c8ef2fa0a92d56df1d9/net/quic/chromium/quic_network_transaction_unittest.cc
[modify] https://crrev.com/30943ee5e8e8b775a6870c8ef2fa0a92d56df1d9/net/quic/chromium/quic_stream_factory.cc
[modify] https://crrev.com/30943ee5e8e8b775a6870c8ef2fa0a92d56df1d9/net/quic/chromium/quic_stream_factory.h

This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Please apply appropriate OSs.  Thanks.

This CL will allow QUIC to failover to TCP to prevent future urgent respins.  It's relatively small and well tested from what I can tell on the CL, and no further merges anticipated.  Approved for M60 branch 3112.

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This already landed here: https://chromium.googlesource.com/chromium/src.git/+/d4087f89dfc467197e431974d2e7e603b7b9d43e

rch@, should we mark as fixed?

Indeed. Good point.