"MemoryTracingTest.BrowserInitiatedDump" is flaky |
|||
Issue description"MemoryTracingTest.BrowserInitiatedDump" 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 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMQsSBUZsYWtlIiZNZW1vcnlUcmFjaW5nVGVzdC5Ccm93c2VySW5pdGlhdGVkRHVtcAw. 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
,
Feb 7 2018
This might be related to bug 809689 since both tests started to flake at around the same time. Lowering priority to P2 since the test is being disabled (on Mac).
,
Feb 7 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3c91290a31a26d12f290d8bc55fe431656307d36 commit 3c91290a31a26d12f290d8bc55fe431656307d36 Author: Guido Urdaneta <guidou@chromium.org> Date: Wed Feb 07 13:52:46 2018 Disable flaky MemoryTracingTest.BrowserInitiatedDump on Mac Bug: 809809 Change-Id: I10b68b7b872c7e08307e1ce6ae653b5680aaf36e TBR: primiano@chromium.org Reviewed-on: https://chromium-review.googlesource.com/906428 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#534997} [modify] https://crrev.com/3c91290a31a26d12f290d8bc55fe431656307d36/content/browser/tracing/memory_tracing_browsertest.cc
,
Feb 7 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by guidou@chromium.org
, Feb 7 2018