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

Issue 868855 link

Starred by 1 user
Status: WontFix
Owner:
█ marpan@chromium.org
Last visit > 30 days ago
Closed: Aug 1
Cc:
asapersson@chromium.org
jianj@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5%-70.9% regression in webrtc_perf_tests at 24129:24130

Project Member Reported by asapersson@chromium.org, Jul 30 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 30 

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

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


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

webrtc-android-tests-nexus72
webrtc-linux-large-tests
webrtc-win-large-tests

Comment 2 by asapersson@chromium.org, Jul 30

Owner: marpan@chromium.org

Comment 3 by marpan@chromium.org, Aug 1

Cc: jianj@chromium.org
The regression in cpu usage is for screenshare test on android only, likely expected from the libvpx roll, but since its on android only we'll leave it as is for now. 

The other regression in for time_between_freezes on linux and windows, not sure this is related to libvpx roll.

Marking as won't fix.

Comment 4 by marpan@chromium.org, Aug 1

Status: WontFix (was: Untriaged)
►

Sign in to add a comment