On 18 December 2015 at 17:01, Michael Henretty <[email protected]> wrote: > > On Fri, Dec 18, 2015 at 10:56 AM, Armen Zambrano Gasparnian > <[email protected]> wrote: >> >> Would separating intermittent test jobs into their own separate job help >> here? >> That way the retry logic can be removed for the more stable tests. > > This is not a bad idea. However, I think the worst part about the "internal" > retry logic is that it hides how bad an intermittent test really is. So > perhaps we could move all the disabled/intermittent tests [1] to a job that > gets hidden on b2g-inbound.
Yes, it is possible to make that specific job a tier-2 (or 3), i.e. hidden, job on Treeherder. However I cannot tell if this approach is better than just disabling these specific tests. It’s my impression that they have been intermittent for such a long time, that they clearly aren’t considered valuable by developers. _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
