Because we've been shipping Aura to canary for a while. And because force compositor...
commit2d050520d564d3d4c527d110deba3943bd378069
authorcpu@chromium.org <cpu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Mon, 16 Sep 2013 00:22:52 +0000 (16 00:22 +0000)
committercpu@chromium.org <cpu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Mon, 16 Sep 2013 00:22:52 +0000 (16 00:22 +0000)
treeb528377c9e85ff78fc33ecbf99a8948f4710dfbc
parent278b6647d6ec9ac03d76d20f76b8c3c65e4c0d47
Because we've been shipping Aura to canary for a while. And because force compositor landed 40 hours ago and things seem ok. See https://codereview.chromium.org/23874016/

This also allows to see perf numbers for Aura.

This has happened before see for example r204698, r211007 and 214056 as an experiment but this time it might stick.

BUG=259185
TEST=none
TBR=scottmg

Review URL: https://codereview.chromium.org/24164002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223293 0039d316-1c4b-4281-b951-d872f2087c98
build/common.gypi