Issue metadata
Sign in to add a comment
|
22.5%-95.4% regression in tab_switching.typical_25 at 459000:459102 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983674435227607152
,
Mar 30 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_11_perf_bisect Benchmark : tab_switching.typical_25 Metric : idle_wakeups_total/idle_wakeups_total Revision Result N chromium@459028 1199.65 +- 105.445 20 good chromium@459102 1173.8 +- 303.419 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 tab_switching.typical_25 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983674435227607152 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6470045531635712 | 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!
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lanwei@chromium.org
, Mar 30 2017