Issue metadata
Sign in to add a comment
|
v8.browsingmobile.runtime_stats:browse_news_cnn failure on chromium.perf at 454171-454196 |
||||||||||||||||||||
Issue descriptionRevision range first seen: 454171-454196 Link to failing step log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus6_Perf__2_%2F5160%2F%2B%2Frecipes%2Fsteps%2Fv8.runtimestats.browsing_mobile%2F0%2Fstdout Going to kick off a bisect now. If the test is disabled, please downgrade to Pri-2.
,
Mar 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8986207904753734240
,
Mar 2 2017
,
Mar 2 2017
,
Mar 2 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : Optimize:count_avg/browse_news/browse_news_cnn Revision Exit Code N chromium@454171 0 +- N/A 3 good chromium@454196 0 +- N/A 3 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn v8.runtimestats.browsing_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8986207904753734240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5296809699704832 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Mar 31 2017
CNN is not the only page that is failing, and that page in particular seems to be flaking at a lower rate than it use to. I"m goign to dupe this into a bug that is just tracking v8.browsingmobile.runtime_stats failures. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by charliea@chromium.org
, Mar 2 2017