New issue
Advanced search Search tips

Issue 629336 link

Starred by 2 users
Status: Fixed
Owner:
yukishiino@chromium.org
Closed: Aug 2016
Cc:
yukishiino@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.9% regression in service_worker.service_worker_micro_benchmark at 402590:402627

Project Member Reported by horo@chromium.org, Jul 18 2016 
See the link to graphs below.

Comment 1 by horo@chromium.org, Jul 18 2016 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=629336

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4s_qpgoM


Bot(s) for this bug's original alert(s):

chromium-rel-win8-dual

Comment 3 by horo@chromium.org, Jul 18 2016

Components: Blink>ServiceWorker
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 19 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jul 29 2016 

Bisect failed: Unknown
Failure reason: the build has failed due to infrastructure failure.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jul 29 2016 

Bisect failed: Unknown
Failure reason: the build has failed due to infrastructure failure.
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Aug 6 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2074
Failure reason: the build has failed due to infrastructure failure.
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Aug 15 2016

Cc: yukishiino@chromium.org
Owner: yukishiino@chromium.org

=== Auto-CCing suspected CL author yukishiino@chromium.org ===

Hi yukishiino@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Adds a crash key to V8EventListener to help diagnose crbug.com/621730 .
Author  : Yuki Shiino
Commit description:
  
This change can be reverted after a day or two of data.

BUG=621730
R=haraken@chromium.org, rsesek@chromium.org

Review URL: https://codereview.chromium.org/2107773002 .

Cr-Commit-Position: refs/heads/master@{#402609}
Commit  : d0210f38391ce7282cab3279a1ddcbff6a975d64
Date    : Wed Jun 29 00:14:04 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@402589  55.865   2.1795    8  good
chromium@402607  54.2344  1.49276   8  good
chromium@402608  53.335   0.253845  5  good
chromium@402609  58.985   1.96796   5  bad    <--
chromium@402610  58.0694  0.897339  8  bad
chromium@402613  59.949   1.50175   5  bad
chromium@402618  58.6406  1.83983   8  bad
chromium@402627  59.651   2.03068   5  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 629336

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests service_worker.service_worker_micro_benchmark
Test Metric: concurrent_100_response_99_percentile/concurrent_100_response_99_percentile
Relative Change: 7.17%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2115
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004299880943291328


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5876523802820608

| 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 Tests>AutoBisect.  Thank you!

Comment 14 by yukishiino@chromium.org, Aug 15 2016

Status: Fixed (was: Assigned)
The CL had already been reverted.
Project Member

Comment 16 by 42576172...@developer.gserviceaccount.com, Aug 20 2016 


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Adds a crash key to V8EventListener to help diagnose crbug.com/621730 .
Author  : Yuki Shiino
Commit description:
  
This change can be reverted after a day or two of data.

BUG=621730
R=haraken@chromium.org, rsesek@chromium.org

Review URL: https://codereview.chromium.org/2107773002 .

Cr-Commit-Position: refs/heads/master@{#402609}
Commit  : d0210f38391ce7282cab3279a1ddcbff6a975d64
Date    : Wed Jun 29 00:14:04 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@402589  55.063   1.82626   5   good
chromium@402608  55.6546  1.95806   12  good
chromium@402609  60.037   2.11253   5   bad    <--
chromium@402610  58.1467  1.93979   12  bad
chromium@402611  58.9883  1.25985   12  bad
chromium@402613  59.1213  2.43708   12  bad
chromium@402618  59.53    1.953     8   bad
chromium@402627  59.897   0.764531  5   bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 629336

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests service_worker.service_worker_micro_benchmark
Test Metric: concurrent_100_response_99_percentile/concurrent_100_response_99_percentile
Relative Change: 8.78%
Score: 99.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2138
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006006658947026816


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5773007935504384

| 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 Tests>AutoBisect.  Thank you!
►

Sign in to add a comment