New issue
Advanced search Search tips

Issue 828353 link

Starred by 1 user
Status: WontFix
Owner:
sprang@chromium.org
Closed: Apr 2018
Cc:
sprang@chromium.org
srte@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2% regression in webrtc_perf_tests at 22438:22444

Project Member Reported by srte@chromium.org, Apr 3 2018 
For some reason, the alert links to the chromium logs, but manually entering the has range in webrtc indicates that this cl might be responsible:
https://webrtc.googlesource.com/src/+/a12b1d625cc992de704b9947c4d11957ebfbc0f8
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 3 2018 

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

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


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

webrtc-win-large-tests

Comment 2 by sprang@chromium.org, Apr 3 2018

Cc: sprang@chromium.org
 Issue 828355  has been merged into this issue.

Comment 3 by sprang@chromium.org, Apr 3 2018 

 Issue 828354  has been merged into this issue.

Comment 4 by sprang@chromium.org, Apr 3 2018 

I think you can assign to an existing bug rather than create a new one in the sheriff ui.

So... The regression is that memory usage has gone down slightly? I think I can live with that. :)

Comment 5 by srte@chromium.org, Apr 3 2018 

Must have accidentally created the duplicates, did not do it on purpose.

Yeah, it should probably be reported as improvements, guess that requires configuring the perf bots.

Comment 6 by sprang@chromium.org, Apr 4 2018

Status: WontFix (was: Assigned)
Yeah. Don't know how to configure that unfortunately. Guess the corp eng pees know.
I'll close this bug then.
►

Sign in to add a comment