Disable flaky layout test for network service.

Disable flaky layout test for network service.

I tried but failed to figure out what was the CL causing this flake.
The earliest bot evidence of it I found was
https://build.chromium.org/p/chromium.fyi/builders/Mojo%20Linux/builds/2402.
The last CL in that blamelist (i.e. the latest CL that might possibly have
caused this problem) was https://chromium-review.googlesource.com/541357.

NOTRY=true
TBR=scottmg@chromium.org
BUG=729849
Review-Url: https://codereview.chromium.org/2957673002
Cr-Commit-Position: refs/heads/master@{#482029}
Committed: https://chromium.googlesource.com/chromium/src/+/5fdcb0640ec1d026572df6a7243257fb88f94aa1

[Randy Smith (Not in Mondays), 2017-06-23 21:02:14]

The CQ bit was checked by rdsmith@chromium.org

[commit-bot: I haz the power, 2017-06-23 21:02:35]

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-06-23 21:07:54]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1498251734766880, "parent_rev":
"bb4aa4a7939b113ebc9fb2cc8437a9f3d24a82a3", "commit_rev":
"5fdcb0640ec1d026572df6a7243257fb88f94aa1"}

[commit-bot: I haz the power, 2017-06-23 21:08:10]

Description was changed from

==========
Disable flaky layout test for network service.

I tried but failed to figure out what was the CL causing this flake.
The earliest bot evidence of it I found was
https://build.chromium.org/p/chromium.fyi/builders/Mojo%20Linux/builds/2402.
The last CL in that blamelist (i.e. the latest CL that might possibly have
caused this problem) was https://chromium-review.googlesource.com/541357.

NOTRY=true
TBR=scottmg@chromium.org
BUG=729849
==========

to

==========
Disable flaky layout test for network service.

I tried but failed to figure out what was the CL causing this flake.
The earliest bot evidence of it I found was
https://build.chromium.org/p/chromium.fyi/builders/Mojo%20Linux/builds/2402.
The last CL in that blamelist (i.e. the latest CL that might possibly have
caused this problem) was https://chromium-review.googlesource.com/541357.

NOTRY=true
TBR=scottmg@chromium.org
BUG=729849

Review-Url: https://codereview.chromium.org/2957673002
Cr-Commit-Position: refs/heads/master@{#482029}
Committed:
https://chromium.googlesource.com/chromium/src/+/5fdcb0640ec1d026572df6a72432...
==========

[commit-bot: I haz the power, 2017-06-23 21:08:12]

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