New issue
Advanced search Search tips

Issue 768539 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

98.7%-100% regression in cc_perftests at 503746:503931

Project Member Reported by benhenry@google.com, Sep 25 2017

Issue description

Wow.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 25 2017

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=e166a00d6abeb7c319b8f09542163b9c01a2685e31288a896de0f6203ea116e5


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

android-nexus6
android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 25 2017


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : cc_perftests
  Metric       : ParamTraits deserialization/num runs in 2 seconds_per_quad_shared_quad_state: DelegatedFrame_Complex


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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8967446304565455408


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
Bisect unable to find culprit, this regression exists in stable. Ignoring.

Sign in to add a comment