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

Issue 750623 link

Starred by 3 users
Status: Assigned
Owner:
█ philipel@chromium.org
Last visit > 30 days ago
Cc:
█ fbarchard@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2% regression in webrtc_perf_tests at 19140:19140

Project Member Reported by philipel@chromium.org, Jul 31 2017
Project Member

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

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

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


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

webrtc-mac-large-tests

Comment 2 by magjed@chromium.org, Jul 31 2017

Owner: fbarchard@chromium.org
Assigning to fbarchard@ to look into if this is caused by libyuv changes.

Comment 3 by fbarchard@google.com, Jul 31 2017 

It shouldnt be libyuv... no recent code changes. June 5 I added HammingDistance.

Comment 4 by fbarchard@chromium.org, Apr 2 2018

Cc: -philipel@chromium.org fbarchard@chromium.org
Owner: philipel@chromium.org
Status: Untriaged (was: Assigned)
The performance regression continues, but I'm pretty sure it wasnt a libyuv change?

Comment 5 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
►

Sign in to add a comment