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

Issue 843467 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug
Hotlist-MemoryInfra



Sign in to add a comment

"Memlog/MemlogBrowserTest.EndToEnd/16" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, May 16 2018

Issue description

"Memlog/MemlogBrowserTest.EndToEnd/16" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRNZW1sb2cvTWVtbG9nQnJvd3NlclRlc3QuRW5kVG9FbmQvMTYM.

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
 
Cc: ajwong@chromium.org
The flakes seem restricted to CrOS, so maybe the test can be disabled on that platform?
Components: Internals>Instrumentation>Memory
Cc: erikc...@chromium.org
Looks like renderer heap dump isn't making it back to the browser. Most likely the renderer is failing to be profiled in the first place, probably due to timing issues with renderer start up. I'll disable the test on chromeos.

883:883:0515/185227.868748:INFO:memlog_browsertest.cc(82)] Memlog mode: 6
[883:883:0515/185227.868773:INFO:memlog_browsertest.cc(83)] Memlog stack mode: 1
[883:883:0515/185227.868779:INFO:memlog_browsertest.cc(84)] Started via command line flag: 1
[883:883:0515/185228.105954:ERROR:test_driver.cc(956)] Failed to find heaps v2 for renderer
[883:883:0515/185228.105985:ERROR:test_driver.cc(623)] Failed to validate renderer allocations
Project Member

Comment 5 by bugdroid1@chromium.org, May 17 2018

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

commit dcc8354d6e7fb4ddad2a1d8aede8edea18e90f9c
Author: Erik Chen <erikchen@chromium.org>
Date: Thu May 17 02:46:30 2018

Disable flaky renderer heap profiling tests on ChromeOS.

The tests recently started flaking. It's unclear why.

Bug: 843467, 843843
Change-Id: Ie5141f65a6da01314da263ab5b875126e4e4fb3e
Reviewed-on: https://chromium-review.googlesource.com/1062834
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559402}
[modify] https://crrev.com/dcc8354d6e7fb4ddad2a1d8aede8edea18e90f9c/chrome/browser/profiling_host/memlog_browsertest.cc

Comment 6 by finnur@chromium.org, May 17 2018

Labels: -Sheriff-Chromium
Owner: erikc...@chromium.org
Status: Assigned (was: Untriaged)
Test disabled and actively being worked on, removing Sheriff label.
Erik, are you the right owner for this bug or can you reassign?

Sign in to add a comment