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

Issue 760109 link

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



Sign in to add a comment

VS 2017 perf regressions

Project Member Reported by pmeenan@chromium.org, Aug 29 2017 
This is a tracking bug for any perf regression alerts as a result of switching to VS 2017 for the weekend.
Project Member

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

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

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


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

chromium-rel-win7-gpu-intel
Project Member

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


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : CastV2Performance_gpu_30fps_fast/capture_duration

Revision             Result                  N
chromium@493983      13.6554 +- 10.8346      21      good
chromium@493986      13.9688 +- 12.6784      21      bad

To Run This Test
  .\src\out\Release_x64\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/8969918151685942528


For feedback, file a bug with component Speed>Bisection

Comment 4 by pmeenan@chromium.org, Aug 29 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment