New issue
Advanced search Search tips

Issue 621200 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

16.4% regression in blink_perf.canvas at 396070:396433

Project Member Reported by majidvp@chromium.org, Jun 17 2016

Issue description

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

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


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

android-galaxy-s5
Trying another bisect.
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 4 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
Trying another bisect.
Project Member

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

Bisect failed: Unknown
Failure reason: the build has failed due to infrastructure failure.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Project Member

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

Bisect failed: Unknown
Failure reason: the build has failed due to infrastructure failure.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/859
Failure reason: the build has failed due to infrastructure failure.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Status: WontFix (was: Assigned)
Bisect failed; only one alert; no ref build results.
Project Member

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


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@396069  7788.31  0.0      1  good

Bisect job ran on: android_s5_perf_bisect
Bug ID: 621200

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: draw-static-webgl-to-hw-accelerated-canvas-2d/draw-static-webgl-to-hw-accelerated-canvas-2d
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/930
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005837426935274000


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

| 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