Issue metadata
Sign in to add a comment
|
No data received for indexeddb_perf from win-high-dpi since 456656 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983983977352815200
,
Mar 27 2017
,
Mar 27 2017
=== Auto-CCing suspected CL author perezju@chromium.org === Hi perezju@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Test failure found with culprit Suspected Commit Author : perezju Commit : 02094452c1bef7590bc74c11f1bf977f53979429 Date : Tue Mar 14 10:26:12 2017 Subject: [tools/perf] Remove indexeddb_perf benchmark Bisect Details Configuration: mac_retina_perf_bisect Benchmark : indexeddb_perf Metric : Total Perf/Total Perf Revision Exit Code N chromium@456615 0 +- N/A 20 good chromium@456644 0 +- N/A 20 good chromium@456658 0 +- N/A 20 good chromium@456665 0 +- N/A 20 good chromium@456666 1 +- N/A 20 bad <-- chromium@456667 1 +- N/A 20 bad chromium@456669 1 +- N/A 20 bad chromium@456672 1 +- N/A 20 bad chromium@456729 1 +- N/A 20 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests indexeddb_perf Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983983977352815200 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5000454557138944 | 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 27 2017
This is intended, the benchmark was removed as per issue 669832 . Annie, could you remove alerting on it?
,
Mar 27 2017
Done. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by toyoshim@chromium.org
, Mar 27 2017