DM: duh, don't calculate digests unless we're going to look at them.

dm/DMReplayTask.h

Index: dm/DMReplayTask.h
diff --git a/dm/DMReplayTask.h b/dm/DMReplayTask.h
index 0ed9351c137ae7c9dc09e52bc859c1fe66a82a31..6a96373f72d274d7fd087631d5e4a4bf8bb72479 100644
--- a/dm/DMReplayTask.h
+++ b/dm/DMReplayTask.h
@@ -10,7 +10,7 @@
 #include "gm.h"
 #include "gm_expectations.h"
 
-// Records a GM through an SkPicture, draws it, and compares against the reference checksum.
+// Records a GM through an SkPicture, draws it, and compares against the reference bitmap.

[epoger, 2013/10/17 16:14:01]

The question is, will DM have the reference bitmap to compare against?  Or will
it be comparing against a checksum?

On Android, we typically want to compare against a checksum (i.e. image hash). 
Otherwise, we have to copy all the reference images down to the device where you
are rendering the test images.  It's much faster to just copy down the
checksums.

 
 namespace DM {
 
@@ -20,8 +20,7 @@ public:
     ReplayTask(const char* name,
                const Task& parent,
                skiagm::GM*,
-               skiagm::GmResultDigest reference,
-               SkBitmap::Config);
+               SkBitmap reference);
 
     virtual void draw() SK_OVERRIDE;
     virtual bool usesGpu() const SK_OVERRIDE { return false; }
@@ -31,8 +30,7 @@ public:
 private:
     const SkString fName;
     SkAutoTDelete<skiagm::GM> fGM;
-    const skiagm::GmResultDigest fReference;
-    const SkBitmap::Config fConfig;
+    const SkBitmap fReference;
 };
 
 }  // namespace DM