remove GM result-grooming tools that use skia-autogen

remove GM result-grooming tools that use skia-autogen

BUG=skia:553
Committed: https://skia.googlesource.com/skia/+/89e884282143e06a9cd2ececcd45642b8d69ab30

[epoger, 2014-06-05 19:33:38]

We are on the verge of deleting our skia-autogen SVN repo (where we have stored
GM actual-result.json files in the past).  See http://skbug.com/553 for details.

The tools within
https://skia.googlesource.com/skia/+/master/gm/rebaseline_server/ (server.py,
download_actuals.py) now download the results from Google Cloud Storage instead
of skia-autogen.

This CL deletes all of our other GM result-grooming tools, which have not been
similarly updated.

I don't believe any of these tools are still needed; if they are, please let me
know and we can evaluate updating them instead of deleting them.

[borenet, 2014-06-05 19:49:58]

LGTM if we're sure none of these are needed.

[epoger, 2014-06-05 20:19:47]

On 2014/06/05 19:49:58, borenet wrote:
> LGTM if we're sure none of these are needed.

That's the $65,536 question.

I'll leave this codereview sitting here for a while, and see if anyone yells.

[Stephen White, 2014-06-05 20:24:48]

On 2014/06/05 20:19:47, epoger wrote:
> On 2014/06/05 19:49:58, borenet wrote:
> > LGTM if we're sure none of these are needed.
> 
> That's the $65,536 question.
> 
> I'll leave this codereview sitting here for a while, and see if anyone yells.

Is rebaseline.py totally broken in the all-git world? If so, I'll reluctantly
let it go. If not, I'd prefer to keep it as a backup plan.

[epoger, 2014-06-05 20:27:53]

On 2014/06/05 20:24:48, Stephen White wrote:
> On 2014/06/05 20:19:47, epoger wrote:
> > On 2014/06/05 19:49:58, borenet wrote:
> > > LGTM if we're sure none of these are needed.
> > 
> > That's the $65,536 question.
> > 
> > I'll leave this codereview sitting here for a while, and see if anyone
yells.
> 
> Is rebaseline.py totally broken in the all-git world? If so, I'll reluctantly
> let it go. If not, I'd prefer to keep it as a backup plan.

It's broken in several ways, none of which is directly related to our git
transition.

Most notable breakage: it only knows how to download GM actual results from
skia-autogen, and skia-autogen gives us fits from time to time.  Hence
http://skbug.com/553

Backup plan to rebaseline_server is to call download_actuals.py , which will
download the images from Google Cloud Storage to your local disk for examination
/ manual diffing.

[Stephen White, 2014-06-05 20:37:07]

On 2014/06/05 20:27:53, epoger wrote:
> On 2014/06/05 20:24:48, Stephen White wrote:
> > On 2014/06/05 20:19:47, epoger wrote:
> > > On 2014/06/05 19:49:58, borenet wrote:
> > > > LGTM if we're sure none of these are needed.
> > > 
> > > That's the $65,536 question.
> > > 
> > > I'll leave this codereview sitting here for a while, and see if anyone
> yells.
> > 
> > Is rebaseline.py totally broken in the all-git world? If so, I'll
reluctantly
> > let it go. If not, I'd prefer to keep it as a backup plan.
> 
> It's broken in several ways, none of which is directly related to our git
> transition.
> 
> Most notable breakage: it only knows how to download GM actual results from
> skia-autogen, and skia-autogen gives us fits from time to time.  Hence
> http://skbug.com/553
> 
> Backup plan to rebaseline_server is to call download_actuals.py , which will
> download the images from Google Cloud Storage to your local disk for
examination
> / manual diffing.

OK, that works for me. Off with their HEADs!

[epoger, 2014-06-09 13:17:54]

The CQ bit was checked by epoger@google.com

[commit-bot: I haz the power, 2014-06-09 13:18:51]

CQ is trying da patch. Follow status at
 https://skia-tree-status.appspot.com/cq/epoger@google.com/320443002/1

[commit-bot: I haz the power, 2014-06-09 13:49:18]

Change committed as 89e884282143e06a9cd2ececcd45642b8d69ab30