New issue
Advanced search Search tips

Issue 743040 link

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



Sign in to add a comment

14.2% regression in performance_browser_tests at 485979:486096

Project Member Reported by nzolghadr@chromium.org, Jul 14 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 14 2017 

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 14 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : TabCapturePerformance/Capture


To Run This Test
  .\src\out\Release\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by sullivan@chromium.org, Aug 21 2017

Status: WontFix (was: Untriaged)
Closing since this dropped down again.
►

Sign in to add a comment