Update perf expecations for Linux-64

Update perf expecations for Linux-64

BUG=139835
NOTRY=TRUE
TBR=simonjam@chromium.org

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=149217

[vandebo (ex-Chrome), 2012-07-31 17:44:19]

James, I don't know if these changes are good, i.e. are these regressions, or
just expected changes, so please review.

chrome-data had three significant steps up since it broke the expectation limit:
149049:149055
149141:149142
149175:149175
All three involved a webkit roll.

the chrome-bss and nacl_helper-bss improvements came from a Nacl Roll: 149187

[sail, 2012-07-31 17:45:38]

lgtm

[commit-bot: I haz the power, 2012-07-31 17:48:27]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/vandebo@chromium.org/10834089/1

[commit-bot: I haz the power, 2012-07-31 17:51:05]

Change committed as 149217

[James Simonsen, 2012-07-31 17:59:03]

https://chromiumcodereview.appspot.com/10834089/diff/1/tools/perf_expectation...
File tools/perf_expectations/perf_expectations.json (left):

https://chromiumcodereview.appspot.com/10834089/diff/1/tools/perf_expectation...
tools/perf_expectations/perf_expectations.json:3:
"linux-release-64/sizes/chrome-si/initializers": {"reva": 145035, "revb":
145035, "type": "absolute", "better": "lower", "improve": 43, "regress": 43,
"tolerance": 0, "sha1": "fa5fa232"},
I think Android will be upset about the new static initializers. CC'ing one of
the leads. I think we'll have to track down where this came from.

[vandebo (ex-Chrome), 2012-07-31 18:01:08]

https://chromiumcodereview.appspot.com/10834089/diff/1/tools/perf_expectation...
File tools/perf_expectations/perf_expectations.json (left):

https://chromiumcodereview.appspot.com/10834089/diff/1/tools/perf_expectation...
tools/perf_expectations/perf_expectations.json:3:
"linux-release-64/sizes/chrome-si/initializers": {"reva": 145035, "revb":
145035, "type": "absolute", "better": "lower", "improve": 43, "regress": 43,
"tolerance": 0, "sha1": "fa5fa232"},
On 2012/07/31 17:59:03, James Simonsen wrote:
> I think Android will be upset about the new static initializers. CC'ing one of
> the leads. I think we'll have to track down where this came from.

Oops, that's supposed to be the chrome-data line, not the chrome-si line.  Will
fix.