New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 751986 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

22.2% regression in speedometer at 490968:491268

Project Member Reported by alexclarke@chromium.org, Aug 3 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 3 2017 

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 3 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total

Revision             Result                  N
chromium@490967      23195.3 +- 13610.8      21      good
chromium@491268      23685.5 +- 4651.94      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by alexclarke@chromium.org, Aug 3 2017

Status: WontFix (was: Untriaged)
Ref moved at the same time, closing.
►

Sign in to add a comment