| commit | 523586a28ed18e6702181cc5d93cd72b23af3fae | |
| author | tonyg@chromium.org <tonyg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 24 Jul 2014 21:12:56 +0000 (24 21:12 +0000) | ||
| committer | tonyg@chromium.org <tonyg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 24 Jul 2014 21:12:56 +0000 (24 21:12 +0000) | ||
| tree | 8da99f0947a2e41403dc5508ede5e000d99f45a3 | treesnapshot (tar.gz zip) |
| parent | 0f156d48f3a7f97b7d07ff83b98f614ff0a94857 | commitdiff |
Re-Reland: [Telemetry] Fix a flake in android browser finder.
It turns out that a few bots have psutils 0.4.1 and the set_cpu_affinity API was
introduced in 0.5. I'm investigating why bots have differing versions, but for
now this patch makes us robust to any psutil version.
BUG=395228
Review URL: https://codereview.chromium.org/407303003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285372 0039d316-1c4b-4281-b951-d872f2087c98
It turns out that a few bots have psutils 0.4.1 and the set_cpu_affinity API was
introduced in 0.5. I'm investigating why bots have differing versions, but for
now this patch makes us robust to any psutil version.
BUG=395228
Review URL: https://codereview.chromium.org/407303003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285372 0039d316-1c4b-4281-b951-d872f2087c98
| tools/telemetry/telemetry/core/backends/chrome/android_browser_finder.py | diffblobblamehistory |