rebaseline blur related outputs

I always got "HTTP Error 500: Internal Server Error", while upload new patch set to this CL.
I'm not sure the uploaded patch sets are correct or not. so I moved the CL to https://codereview.chromium.org/136483002

[zheng.xu, 2014-01-13 12:35:24]

Rebaseline blur related outputs.
The difference are introduced by https://codereview.chromium.org/105893003/,
which will cause CPU side blur output to be different on ARM NEON supported
CPUs.

all blur related outputs(imageblur, imagefilters, spritebitmap) are rebaselined,
except:
1. builder Test-Ubuntu13-ShuttleA-HD2000-x86_64-Debug-TSAN, because expectation
folder for this builder not exists
2. Test-Android-Nexus10-MaliT604-Arm7-Release imagefiltersgraph msaa4, the
output is not correct and it was ignored. I still left the case as ignored.
3. pdf backend which does not support blur. I left them as no-comparison.

NOTE: GPU backend outputs are also reviewed and rebaselined.

[zheng.xu, 2014-01-13 12:54:12]

Sorry, the bots are still generating GM results. Patch set 1 doesn't cover all
the results for all builders. I will upload another patch set to cover all
builders tomorrow.

[Stephen White, 2014-01-13 17:52:23]

On 2014/01/13 12:54:12, zheng.xu wrote:
> Sorry, the bots are still generating GM results. Patch set 1 doesn't cover all
> the results for all builders. I will upload another patch set to cover all
> builders tomorrow.

Your patch should not have affected non-ARM platforms. I'm a little confused as
to why Win7, Win8, ChromeOS Link etc are affected.

Were these platforms changed by another patch?

[Stephen White, 2014-01-13 17:55:55]

On 2014/01/13 17:52:23, Stephen White wrote:
> On 2014/01/13 12:54:12, zheng.xu wrote:
> > Sorry, the bots are still generating GM results. Patch set 1 doesn't cover
all
> > the results for all builders. I will upload another patch set to cover all
> > builders tomorrow.
> 
> Your patch should not have affected non-ARM platforms. I'm a little confused
as
> to why Win7, Win8, ChromeOS Link etc are affected.
> 
> Were these platforms changed by another patch?

Never mind; I see now that those are the new results for the new test case.