New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 808152 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Hotlist-MemoryInfra



Sign in to add a comment

"MemoryTracingBrowserTest.TestBackgroundMemoryInfra" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Feb 1 2018

Issue description

"MemoryTracingBrowserTest.TestBackgroundMemoryInfra" 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 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyPQsSBUZsYWtlIjJNZW1vcnlUcmFjaW5nQnJvd3NlclRlc3QuVGVzdEJhY2tncm91bmRNZW1vcnlJbmZyYQw.

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
 

Comment 1 by yutak@chromium.org, Feb 2 2018

Cc: haraken@chromium.org keishi@chromium.org hajimehoshi@chromium.org
Components: Blink>MemoryAllocator>Partition Internals>Instrumentation>Memory
LeakSanitizer is reporting a lot of leaks in this test.

Can somebody from memory team handle this?

Comment 2 by yutak@chromium.org, Feb 2 2018

Any takers?

Meanwhile, I'm disabling the test on LSAN.

Comment 3 by yutak@chromium.org, Feb 2 2018

See also:  issue 778405 

Comment 4 by yutak@chromium.org, Feb 2 2018

Cc: ssid@chromium.org
+ssid
Project Member

Comment 5 by bugdroid1@chromium.org, Feb 2 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/382f6d5b5ca966fcc9913054cb8d6fd535d7d83c

commit 382f6d5b5ca966fcc9913054cb8d6fd535d7d83c
Author: Yuta Kitamura <yutak@chromium.org>
Date: Fri Feb 02 07:29:29 2018

Disable MemoryTracingBrowserTest.TestBackgroundMemoryInfra on LSAN.

TBR=ssid@chromium.org

Bug: 808152
Change-Id: I50f6ef21551e59aa7aa92f21863b0b24cc2b56c3
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/897237
Reviewed-by: Yuta Kitamura <yutak@chromium.org>
Commit-Queue: Yuta Kitamura <yutak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533987}
[modify] https://crrev.com/382f6d5b5ca966fcc9913054cb8d6fd535d7d83c/chrome/test/base/memory_tracing_browsertest.cc

Comment 6 by yutak@chromium.org, Feb 2 2018

Labels: -Pri-1 Pri-2
Still looking for an owner
Labels: -Sheriff-Chromium
Status: Available (was: Untriaged)

Comment 9 by fdoray@chromium.org, Jun 14 2018

The test also failed on Mac ASan: https://ci.chromium.org/buildbot/chromium.memory/Mac%20ASan%2064%20Tests%20%281%29/41151

Is it also because it produces too much output?
Project Member

Comment 10 by bugdroid1@chromium.org, Jun 14 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1cba7906433960c728fe6865c4cca3640192f323

commit 1cba7906433960c728fe6865c4cca3640192f323
Author: Francois Doray <fdoray@chromium.org>
Date: Thu Jun 14 15:07:16 2018

Disable MemoryTracingBrowserTest.TestBackgroundMemoryInfra on ASan.

TBR=dsinclair@chromium.org

Bug: 808152
Change-Id: I006300209602701c98a5ce35e9d504c1347d8915
Reviewed-on: https://chromium-review.googlesource.com/1101059
Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567267}
[modify] https://crrev.com/1cba7906433960c728fe6865c4cca3640192f323/chrome/test/base/memory_tracing_browsertest.cc

Cc: hjd@chromium.org kouhei@chromium.org kcc@chromium.org lalitm@chromium.org glider@chromium.org
 Issue 778405  has been merged into this issue.

Sign in to add a comment