New issue
Advanced search Search tips

Issue 911120 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Jan 11
Cc:
maxlg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 22% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 611029:612594

Project Member Reported by maxlg@chromium.org, Dec 3 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 3 

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 3 by eroman@chromium.org, Dec 3 

Likely a dupe of  Issue 906540 .
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Dec 5 

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

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.

Comment 5 by maxlg@chromium.org, Jan 11

Status: Fixed (was: Untriaged)
►

Sign in to add a comment