We do in most cases. An SDK roll is kind of an edge case where we update the chromium one but not the devil one.

The alternate solution, and the one I've been working on, is making the perf bots' use of adb consistent by specifying the path everywhere.

Is there a tracking bug for that work this should be duped into?

Should we delete the sdk's copy of adb in order to enforce that all places use catapult's copy?

#4 I don't think so. (In most scenarios, they match anyway.)

Also, revising the issue title. We want to support using different adb binaries in different builds, but a given build should only use one adb binary.

Issue 660997 has been merged into this issue.

Moving Infra>Client>Android -> Infra>Client>Chrome+OS=Android