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

Issue 689970 link

Starred by 2 users
Status: Fixed
Owner:
█ philipel@chromium.org
Last visit > 30 days ago
Closed: Feb 2017
Cc:
hlundin@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 1% regression in webrtc_perf_tests at 16420:16420

Project Member Reported by hlundin@chromium.org, Feb 8 2017

Comment 1 by hlundin@chromium.org, Feb 8 2017 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqLzOugkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6OSqsgkM


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

webrtc-linux-large-tests
webrtc-win-large-tests

Comment 2 by hlundin@chromium.org, Feb 10 2017

Status: Fixed (was: Assigned)
All except one graph have recovered. I think we can mark this as fixed.

Comment 3 by hlundin@chromium.org, Feb 10 2017 

The graph not recovered is WebRTCPerf/webrtc-win-large-tests/webrtc_perf_tests / decode_time / foreman_cif_30kbps_net_delay_0_0_plr_0_H264
►

Sign in to add a comment