Add CSS Transitions performance tests

Add CSS Transitions performance tests

This adds several performance tests for CSS Transitions
initiated in various ways.

BUG=309981, 421733
Committed: https://crrev.com/cd92ffb4655e9ccedaf19d3a787c874b847f89ac
Cr-Commit-Position: refs/heads/master@{#299417}

[alancutter (OOO until 2018), 2014-07-18 09:29:41]

These tests fail to initialise on Android Nexus 7 when the
overlay_background_color_css_transitions.html test is present. It probably runs
out of memory after holding onto 500 600x600 separate compositor layers.

[dtu, 2014-07-24 23:45:50]

On 2014/07/18 09:29:41, alancutter wrote:
> These tests fail to initialise on Android Nexus 7 when the
> overlay_background_color_css_transitions.html test is present. It probably
runs
> out of memory after holding onto 500 600x600 separate compositor layers.

We're running Nexus 7v2 on the perf bots. Does that mean it'll turn the bot red?
Then we can't land.

[alancutter (OOO until 2018), 2014-07-25 05:00:54]

On 2014/07/24 23:45:50, dtu wrote:
> On 2014/07/18 09:29:41, alancutter wrote:
> > These tests fail to initialise on Android Nexus 7 when the
> > overlay_background_color_css_transitions.html test is present. It probably
> runs
> > out of memory after holding onto 500 600x600 separate compositor layers.
> 
> We're running Nexus 7v2 on the perf bots. Does that mean it'll turn the bot
red?
> Then we can't land.

The smoothness.tough_animation_cases is already disabled on Android, possibly
due to overlay_background_color_css_transitions.html.
The overlay test was ported into tough_animation_cases from Blink's
PerformanceTests/Animation, perhaps it can be removed if it's causing redness
since it will still be running over in BlinkPerf.

[dtu, 2014-07-29 22:20:54]

lgtm

[alancutter (OOO until 2018), 2014-10-13 10:20:16]

On 2014/07/29 22:20:54, dtu wrote:
> lgtm

Ran this change through the perf_bisect bots to test.
One was successful
(http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_p...),
the rest failed due to unrelated issue: crbug.com/421755

[alancutter (OOO until 2018), 2014-10-13 10:40:37]

The CQ bit was checked by alancutter@chromium.org

[commit-bot: I haz the power, 2014-10-13 10:41:25]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/399393002/50001

[commit-bot: I haz the power, 2014-10-13 11:54:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-13 11:54:02]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[alancutter (OOO until 2018), 2014-10-14 00:23:15]

The CQ bit was checked by alancutter@chromium.org

[commit-bot: I haz the power, 2014-10-14 00:24:43]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/399393002/50001

[commit-bot: I haz the power, 2014-10-14 01:38:41]

Committed patchset #3 (id:50001)

[commit-bot: I haz the power, 2014-10-14 01:39:22]

Patchset 3 (id:??) landed as
https://crrev.com/cd92ffb4655e9ccedaf19d3a787c874b847f89ac
Cr-Commit-Position: refs/heads/master@{#299417}