tools/android/loading: Force to use of simple cache on desktop.

tools/android/loading/controller.py

Index: tools/android/loading/controller.py
diff --git a/tools/android/loading/controller.py b/tools/android/loading/controller.py
index 1eb2f035b736ba0aadc2425823565cf7b1035d80..758a06b0ced9632c906525612adad86a6e23d1dc 100644
--- a/tools/android/loading/controller.py
+++ b/tools/android/loading/controller.py
@@ -317,6 +317,9 @@ class LocalChromeController(ChromeControllerBase):
        child processes used to run Chrome and XVFB."""
     chrome_cmd = [OPTIONS.local_binary]
     chrome_cmd.extend(self._GetChromeArguments())
+    # Force use of simple cache.
+    # TODO(gabadie): Should we do a SetSimpleCacheBackend(True/False)?

[mattcary, 2016/04/28 09:20:25]

Unless there's going to be a reason to switch between the cache backends, I
support keeping the API simpler and just do what you've done here to make the
simple backend the default. So I think you can remove the TODO.

(The other meta-point is if there's too many TODOs sprinkled through code they
sort of become meaningless and no-one ever does anything about them. I freely
admit I'm bad at this myself... as they say in America, those who can't do,
teach)

[gabadie, 2016/04/28 11:44:07]

Done.
Agreed.

+    chrome_cmd.append('--use-simple-cache-backend=on')
     chrome_cmd.append('--user-data-dir=%s' % self._profile_dir)
     chrome_cmd.extend(['--enable-logging=stderr', '--v=1'])
     # Navigates to about:blank for couples of reasons: