The desktop perf builders use chromium_builder_perf, but the android ones build a list of specific targets. As in https://bugs.chromium.org/p/chromium/issues/detail?id=675712, these targets can be renamed, changed over time, etc. which will then break bisect.

Seems like we should be doing the same as desktop and just building a generic target.

Anybody have a clear idea why the android ones don't use something like chromium_builder_perf as well?