New issue
Advanced search Search tips

Issue 648700 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 666449



Sign in to add a comment

163.2% regression in cc_perftests at 419532:419562

Project Member Reported by jasontiller@chromium.org, Sep 20 2016

Issue description

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

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


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

android-galaxy-s5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 20 2016

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1010
Failure reason: the build has failed.
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/1077
Failure reason: the build has failed.
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.

Owner: ----
perf sheriff fixit: unassigning bugs owned by perf sheriffs to clarify that the rotation is responsible for triage.

Comment 7 by benhenry@google.com, Oct 26 2016

Status: Untriaged (was: Assigned)
Project Member

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


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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@419531  N/A   N/A      0  good
chromium@419562  N/A   N/A      0  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 648700

Test Command: src/build/android/test_runner.py gtest --release -s cc_perftests --verbose
Test Metric: layer_tree_host_frame_time/10_10_threaded_impl_side_leaf_invalidates
Relative Change: 0.00%

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


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

| 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!
Status: WontFix (was: Untriaged)
These will all be invalid as they are specific to Samsung S5s, which we do not trust to give us a signal and have subsequently removed from the waterfalls. If you think this regression is real, please re-open.
Blockedon: 666449

Sign in to add a comment