New issue
Advanced search Search tips

Issue 608476 link

Starred by 1 user
Status: WontFix
Owner:
sullivan@chromium.org
Closed: Dec 2016
Cc:
enne@chromium.org
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 632890


Sign in to add a comment

75.6%-95.2% regression in cc_perftests at 390604:390655

Project Member Reported by lanwei@google.com, May 2 2016 
See the link to graphs below.

Comment 2 by alexclarke@chromium.org, May 9 2016 

Kicked off a couple of bisects.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
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 4 by sheriffbot@chromium.org, Jun 2 2016

Labels: Hotlist-Google

Comment 5 by alexclarke@chromium.org, Jul 8 2016

Labels: -performance-sheriff Performance-Sheriff
Trying another bisect.  Lets see if this one gets anywhere.
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 11 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

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

Comment 8 by lanwei@chromium.org, Jul 29 2016

Cc: sullivan@chromium.org enne@chromium.org
sullivan@, there is a regression here and never been recovered since then. The bisect failed every time because of a build failure. Do you think this bot is not working?

Comment 9 by sullivan@chromium.org, Jul 29 2016

Owner: dtu@chromium.org
Assigning to dtu@ to mark as blocked on the bug he's working on about bisecting cc_perftests

Comment 10 by rsch...@chromium.org, Aug 5 2016 

Dave, ping on this. What's the bug number?

Comment 11 by rsch...@chromium.org, Aug 5 2016

Blockedon: 632890
nvm found it

Comment 12 by dtu@chromium.org, Aug 5 2016

Owner: sullivan@chromium.org
-> sullivan to deploy perf dashboard
Project Member

Comment 14 by 42576172...@developer.gserviceaccount.com, Aug 8 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/900
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 16 by 42576172...@developer.gserviceaccount.com, Aug 8 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/900
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 18 by 42576172...@developer.gserviceaccount.com, Aug 8 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3168
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 20 by 42576172...@developer.gserviceaccount.com, Aug 9 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/905
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 22 by 42576172...@developer.gserviceaccount.com, Aug 9 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/906
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 24 by 42576172...@developer.gserviceaccount.com, Aug 10 2016 

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

Comment 26 by 42576172...@developer.gserviceaccount.com, Aug 10 2016 

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

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

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

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/905
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 32 by 42576172...@developer.gserviceaccount.com, Aug 16 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/906
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 34 by 42576172...@developer.gserviceaccount.com, Aug 18 2016 

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

Comment 36 by 42576172...@developer.gserviceaccount.com, Sep 9 2016 

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

Comment 37 by qyears...@chromium.org, Oct 11 2016 

Perf sheriff ping

Comment 38 by qyears...@chromium.org, Oct 17 2016 

The graphs look clear and this was reproduced across several bots, so likely still worth investigating, but bisect is blocked on 632890.

Comment 39 by qyears...@chromium.org, Oct 17 2016 

 Issue 608486  has been merged into this issue.

Comment 40 by benhenry@google.com, Dec 6 2016

Status: WontFix (was: Assigned)
Sadly, we don't have S5s anymore and this regression was specific to that device.
Project Member

Comment 43 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : cc_perftests
  Metric       : build_raster_task_graph/32_1


To Run This Test
  src/build/android/test_runner.py gtest --release -s cc_perftests --verbose

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982624510972919936

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5280647640252416


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 44 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : cc_perftests
  Metric       : build_raster_task_graph/32_1


To Run This Test
  src/build/android/test_runner.py gtest --release -s cc_perftests --verbose

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982624418692250880

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5285110446817280


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 46 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : cc_perftests
  Metric       : build_raster_task_graph/32_1


To Run This Test
  src/build/android/test_runner.py gtest --release -s cc_perftests --verbose

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982619774304928528

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5343535692251136


| 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 Speed>Bisection.  Thank you!
►

Sign in to add a comment