Issue metadata
Sign in to add a comment
|
Fix and reenable memory.top_7_stress failure on chromium.perf at Nexus 5X WebView |
||||||||||||||||||||
Issue descriptionRevision range first seen: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf%20%282%29/builds/363 Link to failing step log: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf%20%282%29/builds/363/steps/memory.top_7_stress/logs/stdio If the test is disabled, please downgrade to Pri-2.
,
Jun 20 2016
,
Jun 20 2016
Yes it is very possible that my CL broke N5. I will add you to crbug/599656 and resume discussions there.
,
Jun 21 2016
,
Jun 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/dfd52a7ddd4f276eec83f539790c9b2e89bdcce5 commit dfd52a7ddd4f276eec83f539790c9b2e89bdcce5 Author: oysteine <oysteine@chromium.org> Date: Wed Jun 22 09:47:57 2016 Disabling memory.top_7_stress perf test on webview TBR=nednguyen BUG= 621489 Review-Url: https://codereview.chromium.org/2084183003 Cr-Commit-Position: refs/heads/master@{#401241} [modify] https://crrev.com/dfd52a7ddd4f276eec83f539790c9b2e89bdcce5/tools/perf/benchmarks/memory.py
,
Jun 22 2016
,
Jul 18 2016
,
Aug 1 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by oysteine@chromium.org
, Jun 20 2016