On Thu, Jul 20, 2017 at 5:25 PM Mike Hommey <m...@glandium.org
> Another downside is that the exclusion list will only apply to
> changesets that have the changes. Meaning, an excluded job will still
> show up for old changesets that don't have it exluded. Consequently,
> they will still show up for people pushing old trees to try (and they
Is that really a downside though? Presumably if a task was unhidden in the
past, that's because it was stable at that point in time. And if it was
super flaky but for some reason still unhidden, then that's no different
than updating to an old commit that happens to have bustage on it. It's
always a risk.
> The most obvious way to handle this would be for treeherder to use the
> central list of excluded tasks for try...
Heh, true. I'm not sure how exclusion profiles work in treeherder, but if
that's a possibility, that would be a good solution.