Issue metadata
Sign in to add a comment
|
11.8% regression in service_worker.service_worker_micro_benchmark at 474385:474506 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978105716843452560
,
May 31 2017
,
May 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978105644061073184
,
May 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978105639985217488
,
May 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978105626920581760
,
May 31 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile Revision Result N chromium@474384 6.05536 +- 0.554908 14 good chromium@474446 6.01214 +- 0.266042 21 good chromium@474461 5.98048 +- 0.14507 21 unknown chromium@474476 --- --- build failure chromium@474477 5.97714 +- 0.12401 21 bad chromium@474506 5.97964 +- 0.663418 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978105644061073184 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6473081322733568 | 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!
,
May 31 2017
=== Auto-CCing suspected CL author tkent@chromium.org === Hi tkent@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : tkent Commit : a0646d775e805babb8d6949f955071011df709f2 Date : Wed May 24 23:31:38 2017 Subject: Print Preview: Mac: Do not blur focused item while opening the hamburger menu. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile Change : 2.47% | 62.1396428571 -> 60.6475 Revision Result N chromium@474384 62.1396 +- 7.63397 14 good chromium@474445 61.7045 +- 10.2677 21 good chromium@474460 61.9772 +- 6.09286 9 good chromium@474468 60.7729 +- 1.52113 14 good chromium@474472 61.44 +- 0.937203 6 good chromium@474474 61.0294 +- 1.17732 9 good chromium@474475 60.2011 +- 1.12627 9 bad <-- chromium@474506 60.6475 +- 5.73664 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978105716843452560 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5232581890539520 | 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!
,
May 31 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_90_percentile/concurrent_10_response_90_percentile Change : 5.03% | 6.39714285714 -> 6.20428571429 Suspected Commit Range 9 commits in range https://chromium.googlesource.com/chromium/src/+log/eda5652c60377024288d24f9ebc02b42619ebe9d..65b4b99159119398e7fec4dafdbed897153efcc7 Revision Result N chromium@474384 6.39714 +- 0.705149 14 good chromium@474445 6.30952 +- 0.512831 21 good chromium@474476 6.30679 +- 0.335083 14 good chromium@474483 6.32071 +- 0.431559 14 good chromium@474484 --- --- build failure chromium@474485 --- --- build failure chromium@474486 --- --- build failure chromium@474487 --- --- build failure chromium@474488 --- --- build failure chromium@474489 --- --- build failure chromium@474490 --- --- build failure chromium@474491 --- --- build failure chromium@474492 6.22429 +- 0.238522 14 bad chromium@474506 6.20429 +- 0.291364 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978105639985217488 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4680328930656256 | 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!
,
May 31 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: win_8_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile Change : 1.18% | 7.80428571429 -> 7.71214285714 Suspected Commit Range 7 commits in range https://chromium.googlesource.com/chromium/src/+log/dc5014660fb72764d23948e947b7b93ffcd49e9a..adf0a9975c64c1220fa306cb0c2c9d0f9e5f2b6b Revision Result N chromium@474324 7.80429 +- 0.304947 14 good chromium@474328 7.72429 +- 0.211407 14 good chromium@474330 7.76667 +- 0.110378 6 good chromium@474331 --- --- build failure chromium@474332 --- --- build failure chromium@474333 --- --- build failure chromium@474334 --- --- build failure chromium@474335 --- --- build failure chromium@474336 --- --- build failure chromium@474337 7.64333 +- 0.193391 9 bad chromium@474343 7.71036 +- 0.228633 14 bad chromium@474361 7.7175 +- 0.225583 14 bad chromium@474398 7.70595 +- 0.41645 21 bad chromium@474471 7.71214 +- 0.256292 14 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 service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978105626920581760 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6752996421009408 | 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!
,
May 31 2017
My CL is completely unrelated to the benchmark.
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978027499517131312
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978027481540026864
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978027481540026864 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5316648896036864 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978027499517131312 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5268193611874304 | 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!
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978023556569695584
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978023554342911232
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978023556569695584 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5268193611874304 | 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!
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978022468195490768
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978022462874248352
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978022458343719392
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978022452113925776
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978022446134244288
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978022446134244288 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4973010844385280 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978022458343719392 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5287860401340416 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978023554342911232 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5316648896036864 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_90_percentile/concurrent_10_response_90_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978022452113925776 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5766585509216256 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978022462874248352 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5827732287520768 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978022468195490768 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5266709432238080 | 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!
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978019783771881248
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978019781780088640
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978019779909479776
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978019778083403184
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978019776016008016
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978019783771881248 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4973010844385280 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978019781780088640 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5266709432238080 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978019779909479776 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5287860401340416 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_90_percentile/concurrent_10_response_90_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978019778083403184 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5766585509216256 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978019776016008016 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5827732287520768 | 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!
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977987495899968544
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977987487790279248
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977987481419716208
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977987472509130304
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977987481419716208 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4965226081943552 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977987495899968544 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5848694143844352 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977987472509130304 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6593193170173952 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977987487790279248 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5809798920011776 | 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!
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977985810720359200
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977985804656468464
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977985802785526288
,
Jun 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977985800516687920
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977985810720359200 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4965226081943552 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977985802785526288 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5848694143844352 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977985800516687920 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6593193170173952 | 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!
,
Jun 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977985804656468464 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5809798920011776 | 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!
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977939758876415072
,
Jun 2 2017
Bisects were failing due to crbug.com/728594 , restarting this.
,
Jun 2 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: win_8_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile Revision Result N chromium@474324 7.7275 +- 0.216189 14 good chromium@474358 7.75452 +- 0.499745 21 good chromium@474367 7.72738 +- 0.824822 21 unknown chromium@474375 7.67976 +- 0.197671 21 bad chromium@474405 7.66393 +- 0.170906 14 bad chromium@474471 7.68577 +- 0.37887 13 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 service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977939758876415072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5821576794079232 | 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!
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977918929048893440
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977918918443676144
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977918916899900096
,
Jun 2 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile Revision Result N chromium@474384 1.155 +- 0.177059 21 good chromium@474506 1.14405 +- 0.145365 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977918918443676144 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6393122050801664 | 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!
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977914086236235472
,
Jun 2 2017
=== Auto-CCing suspected CL author panicker@chromium.org === Hi panicker@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : panicker Commit : e7366cc17bd54dc1f347e98e40668cf845e472b5 Date : Thu May 25 01:03:37 2017 Subject: Update PaintTiming Web Perf APIs for FP & FCP to report swap time Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile Change : 0.99% | 6.03678571429 -> 5.96464285714 Revision Result N chromium@474384 6.03679 +- 0.234692 14 good chromium@474445 5.99833 +- 0.157692 21 good chromium@474476 6.0575 +- 0.588589 14 good chromium@474489 6.03476 +- 0.733501 21 good chromium@474499 6.02611 +- 0.171723 9 good chromium@474503 6.04214 +- 0.55564 14 good chromium@474504 5.94833 +- 0.0972111 9 bad <-- chromium@474506 5.96464 +- 0.108735 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977918916899900096 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5334964515635200 | 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!
,
Jun 2 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile Revision Result N chromium@474384 1.14571 +- 0.137892 21 good chromium@474506 1.14405 +- 0.0503086 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977914086236235472 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6393122050801664 | 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!
,
Jun 2 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_100_response_50_percentile/concurrent_100_response_50_percentile Change : 0.48% | 61.335952381 -> 61.0419047619 Suspected Commit Range 7 commits in range https://chromium.googlesource.com/chromium/src/+log/a0646d775e805babb8d6949f955071011df709f2..49faaf4047298f4a38df6347704d3fc7e2037539 Revision Result N chromium@474384 61.336 +- 2.44469 21 good chromium@474445 61.7904 +- 6.39035 14 good chromium@474475 62.94 +- 9.66054 14 good chromium@474476 --- --- build failure chromium@474477 --- --- build failure chromium@474478 --- --- build failure chromium@474479 --- --- build failure chromium@474480 --- --- build failure chromium@474481 --- --- build failure chromium@474482 61.1595 +- 7.92373 21 bad chromium@474483 60.9305 +- 5.77459 21 bad chromium@474492 61.075 +- 5.46556 21 bad chromium@474506 61.0419 +- 5.79104 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977918929048893440 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6179070276009984 | 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!
,
Jun 2 2017
The bisect results seem inconclusive?
,
Jun 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977563827204611056
,
Jun 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977563743005167968
,
Jun 6 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977563827204611056 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5868499244679168 | 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!
,
Jun 6 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile Revision Result N chromium@474384 1.15786 +- 0.134271 21 good chromium@474631 1.14548 +- 0.101957 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977563743005167968 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5860743473266688 | 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!
,
Jun 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977559249706483408
,
Jun 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977559247698852976
,
Jun 6 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile Revision Result N chromium@474384 1.13976 +- 0.0614313 21 good chromium@474631 1.14286 +- 0.0409704 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977559249706483408 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5860743473266688 | 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!
,
Jun 6 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile Revision Result N chromium@474384 6.03667 +- 0.507707 21 good chromium@474445 6.04262 +- 0.821907 21 unknown chromium@474506 5.97548 +- 0.190513 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977559247698852976 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5868499244679168 | 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!
,
Jun 9 2017
Bisect didn't finish.. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by horo@chromium.org
, May 31 2017