New issue
Advanced search Search tips

Issue 911504 link

Starred by 1 user
Status: Duplicate
Owner:
oysteine@google.com
Closed: Dec 18
Cc:
cbruni@google.com
fergal@chromium.org
oysteine@google.com
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.4%-565.9% regression in v8.runtime_stats.top_25 at 606972:612292

Project Member Reported by cbruni@google.com, Dec 4 
See the link to graphs below.
Project Member

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

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

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


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

Win 7 Perf
linux-perf

v8.runtime_stats.top_25 - Benchmark documentation link:
  None
Project Member

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

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

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.

Comment 7 by hablich@chromium.org, Dec 17

Components: -Blink>JavaScript Speed>Bisection
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Dec 18 

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

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

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

Cc: oysteine@google.com
Owner: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/155dde1e140000

Perfetto: Add an upper bound to number of events per proto message by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/044129ce84b4e0ea59aaab9398fc9c76b51ae8d2
JavaScript:duration: 4.135 → 5.04 (+0.9056)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

Comment 12 by oysteine@google.com, Dec 18

Mergedinto: 907756
Status: Duplicate (was: Assigned)
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Dec 18

Cc: fergal@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14dde34e140000

Add a testing configuration for HTMLParsingYieldTime study. by fergal@chromium.org
https://chromium.googlesource.com/chromium/src/+/e2fadf24cd0c2c40009b1eb60e38f5ff3e3c859e
JavaScript:duration: 34.64 → 45.58 (+10.94)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None
►

Sign in to add a comment