New issue
Advanced search Search tips

Issue 644431 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Sep 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

41.1% regression in scheduler.tough_scheduling_cases at 416453:416453

Project Member Reported by m...@chromium.org, Sep 6 2016

Issue description

See the link to graphs below.
 

Comment 1 by m...@chromium.org, Sep 6 2016

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

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


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

android-nexus5

Comment 3 by m...@chromium.org, Sep 6 2016

Labels: -Pri-2 Pri-1
Possibly a dup of bug 644403.

Comment 4 by m...@chromium.org, Sep 6 2016

FYI--I'm not including literally hundreds of alerts on the same regression because the UI will not allow me. They will be wisked away as invalid, I guess.

Comment 5 by m...@chromium.org, Sep 6 2016

Mergedinto: 644403
Status: Duplicate (was: Assigned)
Cc: catapult-deps-roller@chromium.org
Owner: catapult-deps-roller@chromium.org

=== Auto-CCing suspected CL author catapult-deps-roller@chromium.org ===

Hi catapult-deps-roller@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 : Roll src/third_party/catapult/ 54acca7c4..4f812c903 (1 commit).
Author  : catapult-deps-roller
Commit description:
  
https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/54acca7c4f74..4f812c9035e6

$ git log 54acca7c4..4f812c903 --date=short --no-merges --format='%ad %ae %s'
2016-09-03 perezju [Telemetry] Switch ShouldTearDownStateAfterEachStoryRun to True as default

BUG= 640990 

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2307273002
Cr-Commit-Position: refs/heads/master@{#416453}
Commit  : 6b6ec1c01c7dac3ee76f9245e4ee442f1c669c55
Date    : Sat Sep 03 11:54:33 2016


===== TESTED REVISIONS =====
Revision                             Mean      Std Dev     N  Good?
chromium@416452                      0.449462  0.00735102  5  good
chromium@416452,catapult@4f812c9035  0.444098  0.00820618  5  good
chromium@416453                      0.622389  0.00738337  5  bad    <--

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 644431

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: queueing_durations/queueing_durations
Relative Change: 38.47%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4092
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002238553771840144


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

| 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