Run skimage on the bots.

slave/skia_slave_scripts/update.py

Index: slave/skia_slave_scripts/update.py
diff --git a/slave/skia_slave_scripts/update.py b/slave/skia_slave_scripts/update.py
index 93c01e56a608d4f7747e24f4888dda8d24ff8278..d35308f2a1ad916220e5a1c7dc95fc16bb4ffe48 100644
--- a/slave/skia_slave_scripts/update.py
+++ b/slave/skia_slave_scripts/update.py
@@ -63,7 +63,8 @@ class Update(BuildStep):
         # Clean our checkout to make sure we don't have a patch left over.
         gclient_utils.Revert()
       gclient_utils.Sync(
-          branches=[solution['name'] for solution in solution_dicts],
+          branches=[solution['name'] for solution in solution_dicts
+                    if not solution['url'].endswith('.git')],

[scroggo, 2013/06/24 17:43:16]

I assume there is some other method we'll be using once we switch everything to
git? My repository is already hosted in git, and running this Sync function on
it tries to rebase onto a commit named <current skia revision> (which doesn't
exist). Skipping it here allows downloading it.

[borenet, 2013/06/25 18:19:12]

Does this actually cause the git repository to be updated?  As I mentioned, I
think we need the Skia code and the corresponding expectations to be locked at
the same commit.  The sensible way to do that is to have them in the same
repository.  If we do that, this problem goes away.

[scroggo, 2013/06/25 19:28:56]

It does, but I agree with your concern about keeping everything in sync.

           revision=self._revision,
           verbose=True,
           manually_grab_svn_rev=True,