Remove dashing from gpu veto

Remove dashing from gpu veto

With new veto our new veto test results look like the following:
TP: true positive (picked to use gpu and gpu was faster)
I: inderminate, the raster time is withing 5% of gpu time

        TP  FP  TN  FN  I

old     21  9   15  12  3
new     29  12  11  6   3

There are three skps that tend to move from TN -> FP, however
the absolute difference in their run times are not huge between
them. The largest being desk_booking which is about 7.1 raster
and 8.8 gpu. The other two skps are desk_yahooanswers and
desk_linkedin

BUG=skia:

Committed: https://skia.googlesource.com/skia/+/12c2198535759ee9aae91ec385e8e31e5dbc12d7

[egdaniel, 2014-06-17 21:21:02]

Here is the version of the veto with dashing removed. Do you think we should we
add anything to the veto for this cl?

[bsalomon, 2014-06-18 13:26:25]

I don't think we should keep the existing dash veto because it is accidentally
veto'ing content that should be vetoed for other reasons.

lgtm

https://codereview.chromium.org/334053005/diff/1/tools/test_gpuveto.py
File tools/test_gpuveto.py (right):

https://codereview.chromium.org/334053005/diff/1/tools/test_gpuveto.py#newcode72
tools/test_gpuveto.py:72: timer_str = 'CPU'
This is going away, Joe is going to remove the CPU timer because it is more
expensive than wall and less accurate.

[egdaniel, 2014-06-18 14:14:50]

The CQ bit was checked by egdaniel@google.com

[commit-bot: I haz the power, 2014-06-18 14:15:16]

CQ is trying da patch. Follow status at
 https://skia-tree-status.appspot.com/cq/egdaniel@google.com/334053005/20001

[commit-bot: I haz the power, 2014-06-18 14:34:43]

Change committed as 12c2198535759ee9aae91ec385e8e31e5dbc12d7