New issue
Advanced search Search tips

Issue 801240 link

Starred by 1 user
Status: Fixed
Owner:
r...@chromium.org
Closed: Feb 2018
Cc:
tguilbert@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.2% regression in media_perftests at 526726:526820

Project Member Reported by tguilbert@chromium.org, Jan 11 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 11 2018 

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

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


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

linux-release

Comment 4 by dtu@chromium.org, Jan 23 2018

Owner: r...@chromium.org
Status: Assigned (was: Untriaged)
Don't know why the Pinpoint jobs didn't post back to this bug on completion. Looks like the clang roll.

Roll clang 318667:321529.
chromium @ 0d72bb1494c94523ae7bd944476a495e8b281bcc

Comment 5 by h...@chromium.org, Feb 21 2018

Status: Fixed (was: Assigned)
Seems this was fixed by the next Clang roll: https://chromeperf.appspot.com/report?sid=dd383018c0351ab7660507f22e3a5d02b28bda8f46428a95e75f55bbc72f2e75&start_rev=526198&end_rev=537767

That roll regressed another variant of the benchmark, see  crbug.com/813851 . It would be interesting to figure out what exactly the benchmark is sensitive about here.
►

Sign in to add a comment