Disabling for Win: https://chromium-review.googlesource.com/c/519122/

Hey tyoshino can you explain why I am owner of this issue?

I was sheriffing. I was simply picking one person from the OWNERS file of the directory in which the test was and assigned tentatively.

Feel free to reassign.

Maybe toyoshim@.

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

commit bf698306c4a097eb809fcf403c12e66358396747
Author: Takashi Toyoshima <toyoshim@chromium.org>
Date: Thu Jun 01 05:24:10 2017

Rewrite ReloadCacheControlBrowserTest

Original tests are flaky because they rely on unwarranted order how
Chrome issues network requests.

New test does not check expectations in an expected order, but
just check if cache control flag is expected one for each resource.

BUG= 726364 ,  728060 

Change-Id: Idb2367a259f22779581ac59b0c0017cd1256f3b9
Reviewed-on: https://chromium-review.googlesource.com/519283
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#476200}
[modify] https://crrev.com/bf698306c4a097eb809fcf403c12e66358396747/content/browser/loader/reload_cache_control_browsertest.cc