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

Issue 744726 link

Starred by 1 user
Status: WontFix
Owner:
█ hubbe@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
Cc:
█ hubbe@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

20.4% regression in media_perftests at 486330:486397

Project Member Reported by hubbe@google.com, Jul 17 2017 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-win10
Project Member

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


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_converter/convert_fifo_only

Revision             Result                  N
chromium@486329      1727676 +- 49809.0      21      good
chromium@486397      1729940 +- 47458.2      21      bad

To Run This Test
  .\src\out\Release_x64\media_perftests.exe --single-process-tests

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by hubbe@chromium.org, Jul 17 2017 

Seems to be a false alert from a test which flips between two possible return values.

Comment 5 by hubbe@chromium.org, Jul 17 2017

Status: WontFix (was: Assigned)
►

Sign in to add a comment