Stop running image tests on msaa.

Stop running image tests on msaa.

Blacklist all image tests on msaa. We do not run them anyway (since
they will not do anything interestingly different from drawing to the
raster backend) - we early exit from Src::draw(), but we still need to
create a render target that matches the size of the image (when not
blacklisted).

Remove the more specific blacklist of a particular image, which is
covered by this one.

BUG=skia:4045
Committed: https://skia.googlesource.com/skia/+/c1121efbc6addc8262b88e8f08ad5a4653fbea62

[scroggo, 2015-07-16 17:24:13]

scroggo@google.com changed reviewers:
+ mtklein@google.com, scroggo@google.com

[scroggo, 2015-07-16 17:24:13]

FYI: I got the following message from presubmit, which is unrelated to my CL:

Traceback (most recent call last):
  File "tools/dm_flags.py", line 216, in <module>
    self_test()
  File "tools/dm_flags.py", line 181, in self_test
    import coverage  # This way the bots don't need coverage.py to be installed.
ImportError: No module named coverage

** Presubmit ERRORS **
`python tools/dm_flags.py test` failed


(Running with --bypass-hooks fixed this, but maybe we can fix this in a better
way?)

PTAL

[mtklein, 2015-07-16 19:17:18]

On 2015/07/16 17:24:13, scroggo wrote:
> FYI: I got the following message from presubmit, which is unrelated to my CL:
> 
> Traceback (most recent call last):
>   File "tools/dm_flags.py", line 216, in <module>
>     self_test()
>   File "tools/dm_flags.py", line 181, in self_test
>     import coverage  # This way the bots don't need coverage.py to be
installed.
> ImportError: No module named coverage
> 
> ** Presubmit ERRORS **
> `python tools/dm_flags.py test` failed
> 
> 
> (Running with --bypass-hooks fixed this, but maybe we can fix this in a better
> way?)
> 
> PTAL

Oh, install python-coverage to run that.  That's usually 
  $ sudo easy_install coverage

[mtklein, 2015-07-16 19:18:43]

On 2015/07/16 19:17:18, mtklein wrote:
> On 2015/07/16 17:24:13, scroggo wrote:
> > FYI: I got the following message from presubmit, which is unrelated to my
CL:
> > 
> > Traceback (most recent call last):
> >   File "tools/dm_flags.py", line 216, in <module>
> >     self_test()
> >   File "tools/dm_flags.py", line 181, in self_test
> >     import coverage  # This way the bots don't need coverage.py to be
> installed.
> > ImportError: No module named coverage
> > 
> > ** Presubmit ERRORS **
> > `python tools/dm_flags.py test` failed
> > 
> > 
> > (Running with --bypass-hooks fixed this, but maybe we can fix this in a
better
> > way?)
> > 
> > PTAL
> 
> Oh, install python-coverage to run that.  That's usually 
>   $ sudo easy_install coverage

(It's not unrelated.  The presubmit runs dm_flags.py's test mode when it
changes.  This mostly just writes out dm_flags.json so you can see things look
like you expect.  It also insists all lines of dm_flags.py have test coverage
from the test cases listed below in the file.  Those are what end up in
dm_flags.json.)

[scroggo, 2015-07-16 19:21:23]

On 2015/07/16 19:18:43, mtklein wrote:
> On 2015/07/16 19:17:18, mtklein wrote:
> > On 2015/07/16 17:24:13, scroggo wrote:
> > > FYI: I got the following message from presubmit, which is unrelated to my
> CL:
> > > 
> > > Traceback (most recent call last):
> > >   File "tools/dm_flags.py", line 216, in <module>
> > >     self_test()
> > >   File "tools/dm_flags.py", line 181, in self_test
> > >     import coverage  # This way the bots don't need coverage.py to be
> > installed.
> > > ImportError: No module named coverage
> > > 
> > > ** Presubmit ERRORS **
> > > `python tools/dm_flags.py test` failed
> > > 
> > > 
> > > (Running with --bypass-hooks fixed this, but maybe we can fix this in a
> better
> > > way?)
> > > 
> > > PTAL
> > 
> > Oh, install python-coverage to run that.  That's usually 
> >   $ sudo easy_install coverage
> 
> (It's not unrelated.  The presubmit runs dm_flags.py's test mode when it
> changes.  This mostly just writes out dm_flags.json so you can see things look
> like you expect.  It also insists all lines of dm_flags.py have test coverage
> from the test cases listed below in the file.  Those are what end up in
> dm_flags.json.)

Alright, coverage is installed now, and dm_flags.json looks good.

[mtklein, 2015-07-16 19:22:40]

On 2015/07/16 19:21:23, scroggo wrote:
> On 2015/07/16 19:18:43, mtklein wrote:
> > On 2015/07/16 19:17:18, mtklein wrote:
> > > On 2015/07/16 17:24:13, scroggo wrote:
> > > > FYI: I got the following message from presubmit, which is unrelated to
my
> > CL:
> > > > 
> > > > Traceback (most recent call last):
> > > >   File "tools/dm_flags.py", line 216, in <module>
> > > >     self_test()
> > > >   File "tools/dm_flags.py", line 181, in self_test
> > > >     import coverage  # This way the bots don't need coverage.py to be
> > > installed.
> > > > ImportError: No module named coverage
> > > > 
> > > > ** Presubmit ERRORS **
> > > > `python tools/dm_flags.py test` failed
> > > > 
> > > > 
> > > > (Running with --bypass-hooks fixed this, but maybe we can fix this in a
> > better
> > > > way?)
> > > > 
> > > > PTAL
> > > 
> > > Oh, install python-coverage to run that.  That's usually 
> > >   $ sudo easy_install coverage
> > 
> > (It's not unrelated.  The presubmit runs dm_flags.py's test mode when it
> > changes.  This mostly just writes out dm_flags.json so you can see things
look
> > like you expect.  It also insists all lines of dm_flags.py have test
coverage
> > from the test cases listed below in the file.  Those are what end up in
> > dm_flags.json.)
> 
> Alright, coverage is installed now, and dm_flags.json looks good.

Add it to the CL?

[mtklein, 2015-07-16 19:22:40]

On 2015/07/16 19:21:23, scroggo wrote:
> On 2015/07/16 19:18:43, mtklein wrote:
> > On 2015/07/16 19:17:18, mtklein wrote:
> > > On 2015/07/16 17:24:13, scroggo wrote:
> > > > FYI: I got the following message from presubmit, which is unrelated to
my
> > CL:
> > > > 
> > > > Traceback (most recent call last):
> > > >   File "tools/dm_flags.py", line 216, in <module>
> > > >     self_test()
> > > >   File "tools/dm_flags.py", line 181, in self_test
> > > >     import coverage  # This way the bots don't need coverage.py to be
> > > installed.
> > > > ImportError: No module named coverage
> > > > 
> > > > ** Presubmit ERRORS **
> > > > `python tools/dm_flags.py test` failed
> > > > 
> > > > 
> > > > (Running with --bypass-hooks fixed this, but maybe we can fix this in a
> > better
> > > > way?)
> > > > 
> > > > PTAL
> > > 
> > > Oh, install python-coverage to run that.  That's usually 
> > >   $ sudo easy_install coverage
> > 
> > (It's not unrelated.  The presubmit runs dm_flags.py's test mode when it
> > changes.  This mostly just writes out dm_flags.json so you can see things
look
> > like you expect.  It also insists all lines of dm_flags.py have test
coverage
> > from the test cases listed below in the file.  Those are what end up in
> > dm_flags.json.)
> 
> Alright, coverage is installed now, and dm_flags.json looks good.

Add it to the CL?

[scroggo, 2015-07-16 19:26:26]

On 2015/07/16 19:22:40, mtklein wrote:
> On 2015/07/16 19:21:23, scroggo wrote:
> > On 2015/07/16 19:18:43, mtklein wrote:
> > > On 2015/07/16 19:17:18, mtklein wrote:
> > > > On 2015/07/16 17:24:13, scroggo wrote:
> > > > > FYI: I got the following message from presubmit, which is unrelated to
> my
> > > CL:
> > > > > 
> > > > > Traceback (most recent call last):
> > > > >   File "tools/dm_flags.py", line 216, in <module>
> > > > >     self_test()
> > > > >   File "tools/dm_flags.py", line 181, in self_test
> > > > >     import coverage  # This way the bots don't need coverage.py to be
> > > > installed.
> > > > > ImportError: No module named coverage
> > > > > 
> > > > > ** Presubmit ERRORS **
> > > > > `python tools/dm_flags.py test` failed
> > > > > 
> > > > > 
> > > > > (Running with --bypass-hooks fixed this, but maybe we can fix this in
a
> > > better
> > > > > way?)
> > > > > 
> > > > > PTAL
> > > > 
> > > > Oh, install python-coverage to run that.  That's usually 
> > > >   $ sudo easy_install coverage
> > > 
> > > (It's not unrelated.  The presubmit runs dm_flags.py's test mode when it
> > > changes.  This mostly just writes out dm_flags.json so you can see things
> look
> > > like you expect.  It also insists all lines of dm_flags.py have test
> coverage
> > > from the test cases listed below in the file.  Those are what end up in
> > > dm_flags.json.)
> > 
> > Alright, coverage is installed now, and dm_flags.json looks good.
> 
> Add it to the CL?

Ah, didn't realize that's how this dance works. Done.

[mtklein, 2015-07-16 19:28:20]

The CQ bit was checked by mtklein@google.com

[mtklein, 2015-07-16 19:28:20]

lgtm

[commit-bot: I haz the power, 2015-07-16 19:28:37]

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

[commit-bot: I haz the power, 2015-07-16 19:36:13]

Committed patchset #3 (id:40001) as
https://skia.googlesource.com/skia/+/c1121efbc6addc8262b88e8f08ad5a4653fbea62