"SingleProcessTracingBrowserTest.TestMemoryInfra" is flaky on Windows |
||||||||||
Issue description"SingleProcessTracingBrowserTest.TestMemoryInfra" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOgsSBUZsYWtlIi9TaW5nbGVQcm9jZXNzVHJhY2luZ0Jyb3dzZXJUZXN0LlRlc3RNZW1vcnlJbmZyYQw. 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 This flaky test/step was previously tracked in issue 584927 .
,
Mar 15 2016
hiroshige@ could you please have a look at this bug? It seems to be related to issue 585026
,
Mar 15 2016
The error message is: > [4340:3244:0314/201527:FATAL:trace_log.cc(537)] Check failed: category_index < MAX_CATEGORY_GROUPS. must increase MAX_CATEGORY_GROUPS Tracing people, is it OK to just increase the MAX_CATEGORY_GROUPS value? Or does this imply an underlying issue to be fixed?
,
Mar 18 2016
Detected 3 new flakes for test/step "SingleProcessTracingBrowserTest.TestMemoryInfra". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOgsSBUZsYWtlIi9TaW5nbGVQcm9jZXNzVHJhY2luZ0Jyb3dzZXJUZXN0LlRlc3RNZW1vcnlJbmZyYQw. 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).
,
Mar 21 2016
It's flaky on Linux too. I'm disabling it now.
,
Mar 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7b1e235fea39faa3c449af2de45606843bba3682 commit 7b1e235fea39faa3c449af2de45606843bba3682 Author: phoglund <phoglund@chromium.org> Date: Mon Mar 21 15:17:25 2016 Disabling flaky SingleProcessTracingBrowserTest.TestMemoryInfra TBR=hiroshige@chromium.org BUG= 594884 Review URL: https://codereview.chromium.org/1819883002 Cr-Commit-Position: refs/heads/master@{#382289} [modify] https://crrev.com/7b1e235fea39faa3c449af2de45606843bba3682/chrome/test/base/tracing_browsertest.cc
,
Mar 21 2016
,
Apr 21 2016
Detected 3 new flakes for test/step "SingleProcessTracingBrowserTest.TestMemoryInfra". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOgsSBUZsYWtlIi9TaW5nbGVQcm9jZXNzVHJhY2luZ0Jyb3dzZXJUZXN0LlRlc3RNZW1vcnlJbmZyYQw. 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).
,
Apr 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8c1a0f0ed6fc47c7ab60a1101045f1f3066bdd18 commit 8c1a0f0ed6fc47c7ab60a1101045f1f3066bdd18 Author: apacible <apacible@chromium.org> Date: Thu Apr 21 19:06:07 2016 Disable flaky SingleProcessTracingBrowserTest TestMemoryInfra on Linux. BUG= 594884 TBR=sky@chromium.org Review URL: https://codereview.chromium.org/1905903003 Cr-Commit-Position: refs/heads/master@{#388836} [modify] https://crrev.com/8c1a0f0ed6fc47c7ab60a1101045f1f3066bdd18/chrome/test/base/tracing_browsertest.cc
,
Apr 21 2016
,
Apr 22 2016
Detected 5 new flakes for test/step "SingleProcessTracingBrowserTest.TestMemoryInfra". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOgsSBUZsYWtlIi9TaW5nbGVQcm9jZXNzVHJhY2luZ0Jyb3dzZXJUZXN0LlRlc3RNZW1vcnlJbmZyYQw. 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).
,
Apr 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ac2aa3b82b8b8f985970a868a79bec9cb6739082 commit ac2aa3b82b8b8f985970a868a79bec9cb6739082 Author: apacible <apacible@chromium.org> Date: Fri Apr 22 18:56:39 2016 Disable flaky SingleProcessTracingBrowserTest TestMemoryInfra. Disable the flaky test completely, similarly to how the flaky multi-process mode for TracingBrowserTest is handled. BUG= 594884 TBR=sky@chromium.org Review URL: https://codereview.chromium.org/1918443002 Cr-Commit-Position: refs/heads/master@{#389189} [modify] https://crrev.com/ac2aa3b82b8b8f985970a868a79bec9cb6739082/chrome/test/base/tracing_browsertest.cc
,
Apr 22 2016
,
Jun 10 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/84b8d0d550280accd6b53af42b0899cda78cdb67 commit 84b8d0d550280accd6b53af42b0899cda78cdb67 Author: ssid <ssid@chromium.org> Date: Fri Jun 10 21:09:03 2016 Re-enable TestMemoryInfra browser tests The single process memory infra tests were failing because the number of tracing categories exceeded the MAX_CATEGORY_GROUPS. This is increased to 200 to suit the needs of single proecss mode (WebView). BUG= 594884 TBR=brettw@chromium.org Review-Url: https://codereview.chromium.org/2043883003 Cr-Commit-Position: refs/heads/master@{#399267} [modify] https://crrev.com/84b8d0d550280accd6b53af42b0899cda78cdb67/base/trace_event/trace_log.cc [modify] https://crrev.com/84b8d0d550280accd6b53af42b0899cda78cdb67/chrome/test/base/tracing_browsertest.cc
,
Jun 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/84b8d0d550280accd6b53af42b0899cda78cdb67 commit 84b8d0d550280accd6b53af42b0899cda78cdb67 Author: ssid <ssid@chromium.org> Date: Fri Jun 10 21:09:03 2016 Re-enable TestMemoryInfra browser tests The single process memory infra tests were failing because the number of tracing categories exceeded the MAX_CATEGORY_GROUPS. This is increased to 200 to suit the needs of single proecss mode (WebView). BUG= 594884 TBR=brettw@chromium.org Review-Url: https://codereview.chromium.org/2043883003 Cr-Commit-Position: refs/heads/master@{#399267} [modify] https://crrev.com/84b8d0d550280accd6b53af42b0899cda78cdb67/base/trace_event/trace_log.cc [modify] https://crrev.com/84b8d0d550280accd6b53af42b0899cda78cdb67/chrome/test/base/tracing_browsertest.cc
,
Jun 21 2016
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by bugdroid1@chromium.org
, Mar 15 2016