New issue
Advanced search Search tips

Issue 913499 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 604544:605339

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

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

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

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


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

Win 7 Nvidia GPU Perf

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

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16b9b0c4140000
Project Member

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/10a50ee4140000
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Dec 20 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/106dfc2e140000
►

Sign in to add a comment