factory can draw now too

expectations/gm/Test-Android-Nexus10-MaliT604-Arm7-Debug/expected-results.json

Index: expectations/gm/Test-Android-Nexus10-MaliT604-Arm7-Debug/expected-results.json
diff --git a/expectations/gm/Test-Android-Nexus10-MaliT604-Arm7-Debug/expected-results.json b/expectations/gm/Test-Android-Nexus10-MaliT604-Arm7-Debug/expected-results.json
index 66953c1837371950d30132df0507549169f1ceac..bde270e5b5de7e30e4b2392af7f2b27a2080f868 100644
--- a/expectations/gm/Test-Android-Nexus10-MaliT604-Arm7-Debug/expected-results.json
+++ b/expectations/gm/Test-Android-Nexus10-MaliT604-Arm7-Debug/expected-results.json
@@ -1756,7 +1756,7 @@
       "allowed-digests": [
         [
           "bitmap-64bitMD5", 
-          8689938548045974643

[epoger, 2013/08/27 15:39:37]

Alas, the fact that an empty image for this test was committed as an expectation
is evidence that people have been committing GM expectations without properly
examining the images.

I take this as a call to:

1. improve the rebaselining tools to make it easier to do proper rebaselines

2. figure out if there is some way to "audit" expectations that were checked in
before the rebaselining tools got easier to use

+          11150486540244810089
         ]
       ], 
       "ignore-failure": false
@@ -1765,7 +1765,7 @@
       "allowed-digests": [
         [
           "bitmap-64bitMD5", 
-          8689938548045974643
+          11150486540244810089
         ]
       ], 
       "ignore-failure": false