fast/frames/cached-frame-counter.html flaky |
|||||
Issue descriptionFlakiness can be seen on Mac trybot. Example builds: https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/289132 https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/289171 https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/289138
,
Jan 25 2017
Who owns Frames? Can we just remove this test? It's marked as SLOW and flakily times out. It was added to test the back/forward cache which does not exist in Chromium: https://bugs.webkit.org/show_bug.cgi?id=33652
,
Jan 25 2017
We don't use the bfcache, but we still keep a subframe count (though it's on FrameHost now). I wonder if we can make this a unit test instead?
,
Feb 21 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 23 2018
It seems the test is not flaky any longer, and TestExpectations doesn't have an entry for this. Closing |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tkent@chromium.org
, Sep 2 2016Status: Available (was: Untriaged)