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

Issue 694622 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

200k regression in sizes at 451412:451412

Project Member Reported by rsch...@chromium.org, Feb 21 2017

Issue description

tansell, looks like this is your change 2bf83ac0e39afbe323a7afe1bd89386ebda50034. Is this expected?
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=694622

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-Ni5_woM


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

mac
Perf sheriff ping.
Labels: binary-size
Summary: 200k regression in sizes at 451412:451412 (was: 0.1% regression in sizes at 451412:451412)
Owner: ----
Status: Unconfirmed (was: Assigned)
This change should have only affected the webkit_layout_tests and related code.

If you take a look at the CL, you should see that either you have the wrong CL or the binary depends on test targets! I know nothing about how the Chrome.app build rules work and why they would are depending on test targets.

Bumping back to unconfirmed and removing myself as owner.





Status: WontFix (was: Unconfirmed)
Not sure what happened with telemetry here, but looking at the graph at this commit:
https://chromeperf.appspot.com/report?sid=5d55db44beb13bb1e813882381fe82b47aa2934496f2e59840f8ee908da122ca&rev=451412

There is zero size change.
Labels: -binary-size Performance-Size

Sign in to add a comment