Setting up the FakeUpdateChecker is causing problems on the Tarako. Since there's not much engineering support in figuring out why this is, I'd like to make this step optional, but enabled by default, so we can skip it when running b2gperf.

Comment on attachment 8372509 [details] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/16094 I really hate adding new command lines switches, they are like a bad disease and it makes it harder to teach, use and document the code. You set a bad precedent to use one to band-aid something that doesn't work rather than fix the atom in the first place. I'd much rather see the atom fixed properly, to detect whether it can run or not and skip and also to output to the logs when it was not run.

Fair point, I'll do that.

(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #4) > https://hg.mozilla.org/integration/mozilla-inbound/rev/00d49079bcbc This was from bug 969654, sorry for the spam.

It appears this is no longer necessary; the b2gperf jobs are running against Tarako devices, so I'm going to punt on this.