Issue metadata
Sign in to add a comment
|
98.7%-100% regression in cc_perftests at 503746:503931 |
||||||||||||||||||||
Issue descriptionWow.
,
Sep 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8967446304565455408
,
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
,
Dec 12 2017
Bisect unable to find culprit, this regression exists in stable. Ignoring. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 25 2017