"RenderViewBrowserTest.ConfirmCacheInformationPlumbed" is flaky |
|||||||
Issue description"RenderViewBrowserTest.ConfirmCacheInformationPlumbed" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 7 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyPwsSBUZsYWtlIjRSZW5kZXJWaWV3QnJvd3NlclRlc3QuQ29uZmlybUNhY2hlSW5mb3JtYXRpb25QbHVtYmVkDA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Mar 10 2017
Megan, Dmitry: What's the current status of the offline work? Are you still involved or do you know who is? The basic question I have is whether the information as to whether there is stale info in the cache (which I used to control whether to show the "Show saved copy" button) is likely to be needed in the future or if it should just be ripped out.
,
Mar 10 2017
Hi Randy, my team works on offline a lot, but "show cached copy" from HTTP cache is not what we do (our thing is to save DOM snapshot and use this as a static representation while offline). Also adding Tal to chime in on the future plans for the "Show Cached Copy" experiment.
,
Mar 10 2017
Dmitry, just to be clear: None of the work your group is doing or is expecting to do in the near future is planning to use stale information in the HTTP cache? (I don't think there's a future for the "Show saved copy" experiment in and of itself; it was just grist for the larger offline planning.) Tal: My guess is that if Dmitry's not doing it it's not being done, but just to confirm: All the offline work is in his group? If not, are you aware of work being done that would use stale information in the HTTP cache? If not, we should rip this code out.
,
Mar 10 2017
We are not planning to use stale info in the cache, but we might not be the only group. Adding BenGr, I believe between him/Megan/Tal/me you get all possible suspects :)
,
Mar 15 2017
Megan should know what's going on.
,
Mar 15 2017
The experiment was turned off in 2015. I don't see why we wouldn't want to rip out this code, unless Tal has any other plans for it.
,
Feb 16 2018
Sorry, dropping this on the floor since I'm leaving Chromium development.
,
Jun 1 2018
Detected 3 new flakes for test/step "RenderViewBrowserTest.ConfirmCacheInformationPlumbed". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyPwsSBUZsYWtlIjRSZW5kZXJWaWV3QnJvd3NlclRlc3QuQ29uZmlybUNhY2hlSW5mb3JtYXRpb25QbHVtYmVkDA. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).
,
Jun 4 2018
This happened temporarily and stopped again. Closing for now. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by guidou@chromium.org
, Mar 10 2017Owner: rdsmith@chromium.org
Status: Assigned (was: Untriaged)