New issue
Advanced search Search tips

Issue 828025 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

16.1%-18.9% regression in blink_perf.parser at 547155:547291

Project Member Reported by pmeenan@chromium.org, Apr 2 2018

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=828025

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


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

chromium-rel-win7-x64-dual
chromium-rel-win8-dual
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11905b9f440000
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/118035cf440000
Owner: jbroman@chromium.org
Status: Assigned (was: Untriaged)
Assigning to benchmark owner jbroman: the bisects failed to complete, but it looks like they did find a regression at r547209, "Update ThreadSpecific to use base::ThreadLocalStorage.": https://pinpoint-dot-chromeperf.appspot.com/job/118035cf440000

But the graphs all recovered. Is it worth assigning to the CL owner to investigate further?
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 15 2018


Previous job on this bug failed due to https://github.com/catapult-project/catapult/issues/4393, retrying now that it's fixed.

Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 15 2018

📍 Pinpoint job started.
https://chromeperf.appspot.com/job/1488733ac40000
Cc: -pmeenan@chromium.org

Sign in to add a comment