+jbudorick

I checked a few of the failing builds, and they're from src@(~Oct/Sept) while the passing ones were from src@(~last week). My guess is that maybe chrome_modern_public_apk didn't exist as a target back then? We had a recent change to force the android perf builders to build specific targets, maybe we should just have them build everything? wdyt?

This is probably due to N SDK update. Anything older than that will not work anymore. 

Simon - have you seen any builds/bisects that failed with this same error that were testing over revision ranges during that time? We're going to have to wontfix them if so.

#1: Correct, chrome_modern_public_apk was added Nov 9: https://chromium.googlesource.com/chromium/src/+/be18d7c8226d8949d9b840a99b365e032697becf

#3: per the above, this is not due to the N SDK.

So should we just go ahead and build some generic "all" target and re-introduce these targets at a later date?

I guess so, though all will be significantly slower.

I don't know the exact number, but there seem to be a handful of regressions from pre-Nov 9 still being investigated, so maybe what we can do is:

- Fix this for now by just building all (that's what it used to do anyway)
- At some point in next few months switch back to building specific targets (or even get chromium_builder_perf working for android?), let perf sheriffs know this will happen and we won't be able to bisect older regressions, and WontFix the older regressions.

What does everyone think?

benhenry: Can you help us figure out which regressions from before November 9 are most important to bisect?

Looks like we have 149 alerts that are still open. I'm going to narrow this down more to see which don't need bisect and report back.

https://bugs.chromium.org/p/chromium/issues/list?can=2&q=opened%3C2016-11-09+Performance%3DSheriff+Android&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

Here are 21 that would provide a decent value:
https://bugs.chromium.org/p/chromium/issues/list?can=2&q=opened%3C2016-11-09+Performance%3DSheriff+Android+-has%3Aowner+modified%3E2016-12-01&sort=modified&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

The rest that I found are old, repeats, etc. 

https://bugs.chromium.org/p/chromium/issues/list?can=2&q=opened%3C2016-11-09+Performance%3DSheriff+Android+-has%3Aowner+modified%3E2016-12-01+-label%3ARestrict-View-Google&sort=modified&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

Brings this down to 9

Only the external android bots are affected by this.

Chatting offline w/ Annie/Dave, feeling here is that we can leave as is. If anybody pursues those we can revisit the "all" fix.