New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 880438 link

Starred by 1 user
Status: Closed
Owner: ----
Closed: Nov 21
Cc:
maxlg@chromium.org
█ v8-ci-au...@chops-service-accounts.iam.gserviceaccount.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2% regression in jetstream at 587526:587610

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

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

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

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


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

linux-perf

jetstream - Benchmark documentation link:
  None
Project Member

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

Cc: v8-ci-au...@chops-service-accounts.iam.gserviceaccount.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/130e57b9640000

Version 7.0.276 by v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com
https://chromium.googlesource.com/v8/v8/+/6e2adae6f7f8e891cfd01f3280482b20590427a6
201.9 → 199.9 (-2.017)

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

Benchmark documentation link:
  None

Comment 4 by maxlg@chromium.org, Nov 21

Status: Closed (was: Assigned)
The regression is caused by reverting a recent improvement
►

Sign in to add a comment