Disable GPU Raster for non-GPU-specific LayoutTests

Disable GPU Raster for non-GPU-specific LayoutTests

With Gpu Raster landing on mac, layout tests may inadvertantly start
being run with Gpu Raster enabled. This isn't desireable as it
introduces variability into the layout tests depending on the Gpu.

A small subset of LayoutTests specifically target GPU - in these cases
we leave the previous behavior unchanged.

BUG=542959
Committed: https://crrev.com/6929f4cf2946247bebde651d406e5d3fa2aedfbc
Cr-Commit-Position: refs/heads/master@{#391609}

[ericrk, 2016-05-04 00:19:37]

ericrk@chromium.org changed reviewers:
+ piman@chromium.org

[ericrk, 2016-05-04 00:27:29]

Description was changed from

==========
Disable GPU Raster for non-GPU-specific LayoutTests

With Gpu Raster landing on mac, layout tests may inadvertantly start
being run with Gpu Raster enabled. This isn't desireable as it
introduces variability into the layout tests depending on the Gpu.
Additionally, running with MESA is not a performance hit we'd like to
take.

A small subset of LayoutTests specifically target GPU - in these cases
we leave the previous behavior unchanged.

BUG=542959
==========

to

==========
Disable GPU Raster for non-GPU-specific LayoutTests

With Gpu Raster landing on mac, layout tests may inadvertantly start
being run with Gpu Raster enabled. This isn't desireable as it
introduces variability into the layout tests depending on the Gpu.

A small subset of LayoutTests specifically target GPU - in these cases
we leave the previous behavior unchanged.

BUG=542959
==========

[piman, 2016-05-04 00:44:20]

LGTM, but do we have a GPU bot that runs all layout tests in gpu mode?

[ericrk, 2016-05-04 18:34:50]

On 2016/05/04 00:44:20, piman wrote:
> LGTM, but do we have a GPU bot that runs all layout tests in gpu mode?

I believe we run layout tests on GPU bots for some GPU specific tests
(virtual/gpu-rasterization). For now the goal is to stop additional tests from
using GPU raster.

[ericrk, 2016-05-04 18:34:57]

The CQ bit was checked by ericrk@chromium.org

[commit-bot: I haz the power, 2016-05-04 18:35:24]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1949883002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1949883002/1

[commit-bot: I haz the power, 2016-05-04 20:03:51]

Description was changed from

==========
Disable GPU Raster for non-GPU-specific LayoutTests

With Gpu Raster landing on mac, layout tests may inadvertantly start
being run with Gpu Raster enabled. This isn't desireable as it
introduces variability into the layout tests depending on the Gpu.

A small subset of LayoutTests specifically target GPU - in these cases
we leave the previous behavior unchanged.

BUG=542959
==========

to

==========
Disable GPU Raster for non-GPU-specific LayoutTests

With Gpu Raster landing on mac, layout tests may inadvertantly start
being run with Gpu Raster enabled. This isn't desireable as it
introduces variability into the layout tests depending on the Gpu.

A small subset of LayoutTests specifically target GPU - in these cases
we leave the previous behavior unchanged.

BUG=542959
==========

[commit-bot: I haz the power, 2016-05-04 20:03:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-04 20:04:51]

Description was changed from

==========
Disable GPU Raster for non-GPU-specific LayoutTests

With Gpu Raster landing on mac, layout tests may inadvertantly start
being run with Gpu Raster enabled. This isn't desireable as it
introduces variability into the layout tests depending on the Gpu.

A small subset of LayoutTests specifically target GPU - in these cases
we leave the previous behavior unchanged.

BUG=542959
==========

to

==========
Disable GPU Raster for non-GPU-specific LayoutTests

With Gpu Raster landing on mac, layout tests may inadvertantly start
being run with Gpu Raster enabled. This isn't desireable as it
introduces variability into the layout tests depending on the Gpu.

A small subset of LayoutTests specifically target GPU - in these cases
we leave the previous behavior unchanged.

BUG=542959

Committed: https://crrev.com/6929f4cf2946247bebde651d406e5d3fa2aedfbc
Cr-Commit-Position: refs/heads/master@{#391609}
==========

[commit-bot: I haz the power, 2016-05-04 20:04:52]

Patchset 1 (id:??) landed as
https://crrev.com/6929f4cf2946247bebde651d406e5d3fa2aedfbc
Cr-Commit-Position: refs/heads/master@{#391609}