"org.chromium.chrome.browser.profiling_host.ProfilingProcessHostAndroidTest#testModeRendererPseudo" is flaky |
||
Issue description"org.chromium.chrome.browser.profiling_host.ProfilingProcessHostAndroidTest#testModeRendererPseudo" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNybAsSBUZsYWtlImFvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIucHJvZmlsaW5nX2hvc3QuUHJvZmlsaW5nUHJvY2Vzc0hvc3RBbmRyb2lkVGVzdCN0ZXN0TW9kZVJlbmRlcmVyUHNldWRvDA. 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
,
Jan 18 2018
Issue 803578 has been merged into this issue.
,
Jan 18 2018
From logcat, here are the 3 sources of errors: """ 01-18 18:44:20.279 8319 8497 E chromium: [ERROR:devtools_http_handler.cc(249)] Cannot start http server for devtools. Stop devtools. 01-18 18:44:20.729 8319 8334 E chromium: [ERROR:profiling_test_driver.cc(586)] Failed to find heaps v2 for renderer 01-18 18:44:20.729 8319 8334 E chromium: [ERROR:profiling_test_driver.cc(363)] Failed to validate renderer allocations """ The reason that "failed to find heaps v2" happens is because profiling hasn't started for the renderer. This is because we have no way of waiting for profiling to start before taking the dump. I'll disable the test on android.
,
Jan 19 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/24afdee73d1ca3b12a2267e10579c02c0bdc74d1 commit 24afdee73d1ca3b12a2267e10579c02c0bdc74d1 Author: erikchen <erikchen@chromium.org> Date: Fri Jan 19 00:37:17 2018 Get rid of renderer and GPU OOP HP tests for Android. There's currently no mechanism to wait until profiling has started. This means that the results are racy, and sometimes don't contain heap dumps for the respective processes. Bug: 803568 Change-Id: I28b4ba5f741daaec7a8933cfd6c028abb8f83822 Reviewed-on: https://chromium-review.googlesource.com/874796 Reviewed-by: Dmitry Skiba <dskiba@chromium.org> Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#530366} [modify] https://crrev.com/24afdee73d1ca3b12a2267e10579c02c0bdc74d1/chrome/android/javatests/src/org/chromium/chrome/browser/profiling_host/ProfilingProcessHostAndroidTest.java
,
Jan 19 2018
bug to re-enable the tests: https://bugs.chromium.org/p/chromium/issues/detail?id=803696 |
||
►
Sign in to add a comment |
||
Comment 1 by smcgruer@chromium.org
, Jan 18 2018Owner: erikc...@chromium.org
Status: Assigned (was: Untriaged)