New issue
Advanced search Search tips

Issue 922492 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 16
Cc:
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3%-238.1% regression in queueing_durations,tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 622850:622869

Project Member Reported by 42576172...@developer.gserviceaccount.com, Jan 16 (6 days ago) 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 16 (6 days ago) 

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

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


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

linux-perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jan 16 (6 days ago) 

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11e8ad6c540000
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 16 (6 days ago) 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11e8ad6c540000

All of the runs failed. The most common error (20/20 runs) was:
ReadValueError: Could not find values matching: {'story': u'repaint_yahoo_homepage_2018', 'histogram': u'thread_raster_cpu_time_per_frame'}

Comment 4 by sullivan@chromium.org, Jan 16 (6 days ago)

Status: WontFix (was: Untriaged)
Looks like a return to normal values after a blip.
►

Sign in to add a comment