Workaround python time.strptime flake in Android tests

In general time.strptime is not threadsafe in python: [1]. This causes
flaky errors on various bots that test Android because catapult [2]
talks to devices from different threads (for multiple reasons).

One observation in the python bug ([1]) says that only importing parts
of strptime is racy, so importing it early enough before any threading
is started would remove this kind of flake.

This workaround is used in other parts of chromium and catapult itself,
so we can probably be more preventive by doing it in a central place.
For now let's just reduce the flake.

[1] time.strptime not thread safe
    https://bugs.python.org/issue7980

[2] Catapult is the home for several performance tools that span from
    gathering, displaying and analyzing performance data.
    https://github.com/catapult-project/catapult

BUG=724524

Review-Url: https://codereview.chromium.org/2891403002
Cr-Commit-Position: refs/heads/master@{#473545}
1 file changed