Revert of Add a whitelist for QUIC hosts.

Revert of Add a whitelist for QUIC hosts. (patchset #7 id:140001 of https://codereview.chromium.org/1580583002/ )

Reason for revert:
Speculative revert for Android Cronet bots failure (CronetTestInstrumentation)

Original issue's description:
> Add a whitelist for QUIC hosts.
>
> BUG=576402
>
> Committed: https://crrev.com/1ad82bbc44d87669926c9cffe2ba77564df420a3
> Cr-Commit-Position: refs/heads/master@{#368810}

TBR=agl@chromium.org,rsleevi@chromium.org,rch@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=576402
Committed: https://crrev.com/d940c626454dcf80efdcff9c40dd99ba055fb2b2
Cr-Commit-Position: refs/heads/master@{#369050}

[trchen, 2016-01-13 00:23:33]

Created Revert of Add a whitelist for QUIC hosts.

[commit-bot: I haz the power, 2016-01-13 00:24:39]

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

[commit-bot: I haz the power, 2016-01-13 00:28:03]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-13 00:29:21]

Description was changed from

==========
Revert of Add a whitelist for QUIC hosts. (patchset #7 id:140001 of
https://codereview.chromium.org/1580583002/ )

Reason for revert:
Speculative revert for Android Cronet bots failure (CronetTestInstrumentation)

Original issue's description:
> Add a whitelist for QUIC hosts.
> 
> BUG=576402
> 
> Committed: https://crrev.com/1ad82bbc44d87669926c9cffe2ba77564df420a3
> Cr-Commit-Position: refs/heads/master@{#368810}

TBR=agl@chromium.org,rsleevi@chromium.org,rch@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=576402
==========

to

==========
Revert of Add a whitelist for QUIC hosts. (patchset #7 id:140001 of
https://codereview.chromium.org/1580583002/ )

Reason for revert:
Speculative revert for Android Cronet bots failure (CronetTestInstrumentation)

Original issue's description:
> Add a whitelist for QUIC hosts.
>
> BUG=576402
>
> Committed: https://crrev.com/1ad82bbc44d87669926c9cffe2ba77564df420a3
> Cr-Commit-Position: refs/heads/master@{#368810}

TBR=agl@chromium.org,rsleevi@chromium.org,rch@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=576402

Committed: https://crrev.com/d940c626454dcf80efdcff9c40dd99ba055fb2b2
Cr-Commit-Position: refs/heads/master@{#369050}
==========

[commit-bot: I haz the power, 2016-01-13 00:29:22]

Patchset 1 (id:??) landed as
https://crrev.com/d940c626454dcf80efdcff9c40dd99ba055fb2b2
Cr-Commit-Position: refs/heads/master@{#369050}

[Ryan Sleevi, 2016-01-13 00:35:29]

Not LGTM.

We should not be reverting for FYI bots.

[trchen, 2016-01-13 00:47:26]

On 2016/01/13 00:35:29, Ryan Sleevi wrote:
> Not LGTM.
> 
> We should not be reverting for FYI bots.


What is your recommended way to proceed? The instruction on
https://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium
suggests "In all cases, the preferred way of dealing with alerts is to revert
the offending patch, even if the failure does not close the tree.".

Let me know what is the better practice and I will do that next time. Thanks!

[Ryan Sleevi, 2016-01-13 00:53:10]

On 2016/01/13 00:47:26, trchen wrote:
 
> What is your recommended way to proceed? The instruction on
> https://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium
> suggests "In all cases, the preferred way of dealing with alerts is to revert
> the offending patch, even if the failure does not close the tree.".
> 
> Let me know what is the better practice and I will do that next time. Thanks!

If it's an FYI bot (e.g. no trybot, not on the CQ, not reproducible by any
developer), then you handle it asynchronously

From https://www.chromium.org/developers/tree-sheriffs
"For bots that are not covered by the Commit Queue and if the author is online,
it's fine to ask them to fix asynchronously (since it shouldn't be blocking
anyone, and it's not the author's fault as the change landed through the CQ)."

Basically, if it's not on the CQ, it's strongly discouraged from reverting, and
the bot owner(s) / sheriffs are the ones that should drive the investigation and
green-ing the bot.