New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 659044 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 659046
Owner: ----
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 659094



Sign in to add a comment

2.9% regression in thread_times.key_idle_power_cases at 426992:426992

Project Member Reported by alexclarke@chromium.org, Oct 25 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=659044

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


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

android-one
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 25 2016

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1754
Failure reason: the build has failed due to infrastructure failure.

Blockedon: 659094
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 25 2016


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev     N   Good?
chromium@426991  0.501401  0.00396546  18  good
chromium@426992  0.502036  0.00285171  18  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 659044

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: thread_total_all_cpu_time_per_second/set-timeout.html
Relative Change: 0.23%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1753
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997836753482214496


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

| 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!
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Oct 25 2016

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1758
Failure reason: the build has failed due to infrastructure failure.

Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Dec 17 2016

Mergedinto: 659046
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : Use TRACE_TASK_EXECUTION in SequencedWorkerPool.
Author  : fdoray
Commit description:
  
With this CL, SequencedWorkerPool generates an event in the "toplevel"
category when it runs a task. This is the same behavior as MessageLoop,
TaskScheduler and WorkerPool.

BUG= 611818 

Review-Url: https://chromiumcodereview.appspot.com/2429863002
Cr-Commit-Position: refs/heads/master@{#426994}
Commit  : af4072ecf86c2c8ff7ec217e4830e2c2e5964cf7
Date    : Sun Oct 23 13:41:49 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev     N  Good?
chromium@426990  0.506091  0.00930673  6  good
chromium@426992  0.503937  0.0144731   9  good
chromium@426993  0.501966  0.0105156   6  good
chromium@426994  0.519177  0.011591    6  bad    <--
chromium@426997  0.519463  0.0171274   6  bad
chromium@427003  0.517928  0.0106116   6  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 659044

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html thread_times.key_idle_power_cases
Test Metric: thread_total_all_cpu_time_per_second/set-timeout.html
Relative Change: 2.34%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1883
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993074520227235344


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

| 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