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

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


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

Google Chrome Linux x64

One possibility is 01e0dea8ecdfb80206af68a20bc795f059f25c23. zqzhang, does this data end up in the binary? Because it would make sense to see a Linux bump if so.

The moved data files are only for tests, and is not included in the binary.

Any update on this bug?

@dtu: are you working on making regression size bisectable?

I think we need to reassign the bug.

@dtu : Could you please take a look into this and update further if any.

nednguyen@: no, we are building every commit on the perf waterfall. Starting in May, every sizes regression has 1 commit in its range on Android, Mac, and Linux.

None of the changes seem plausible (https://chromium.googlesource.com/chromium/src/+log/9cd8ccc773bd2d4b972fb56ee9327903799dee26..34f2e5e23e6a3a34742089fc49590075d4352685).

Given the magnitude of the change, I think it's reasonable to just WontFix this.