Actually, looks like the test is still flaky. In a recent build, it again produced unexpected text output: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/368682.
DIFF:
--- /b/rr/tmpsebRj2/w/layout-test-results/http/tests/inspector/network/network-filters-expected.txt
+++ /b/rr/tmpsebRj2/w/layout-test-results/http/tests/inspector/network/network-filters-actual.txt
@@ -46,10 +46,10 @@
filterText: is:from-cache
isRegex: false
-Found results: 1
+Found results: 3
filterText: -is:from-cache
isRegex: false
-Found results: 3
+Found results: 1
Hmmmm, The recent changes to reusing memory cache is the culprit. I may have been wrong with enable/disable cache in devtools to clear the cache. I know it does clear the cache, but it may do it lazily so if the test runs to fast it won't clear it.
We have a few of these in our protocol. I will talk to our tech lead and see what the priority on this is.
Thanks!
Comment 1 by bugdroid1@chromium.org
, Jan 6 2017