While working on the integration of the YouTube playback performance tests into Raptor, and correctly reporting the results to perfherder I noticed a really [high noise](https://treeherder.mozilla.org/perf.html#/graphs?timerange=604800&series=try,2009309,1,10&series=try,2010930,1,10&series=try,2009305,1,10&series=try,2009297,1,10&series=try,2009939,1,10&selected=try,2010930,473205,807137661,10 ) for Aarch64 and MacOS, which requires us to disable alerting for those platforms. Sadly Perfherder doesn't allow to enable / disable alerting for specific platforms or tests whether on the suite nor sub-test level. Instead the results as pushed by the client have to be updated, by having `alert_on` set appropriately. It would be great if sheriffs could manage that via perfherder directly.
Bug 1551556 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
While working on the integration of the YouTube playback performance tests into Raptor, and correctly reporting the results to perfherder I noticed a really [high noise](https://treeherder.mozilla.org/perf.html#/graphs?timerange=604800&series=try,2009309,1,10&series=try,2010930,1,10&series=try,2009305,1,10&series=try,2009297,1,10&series=try,2009939,1,10&selected=try,2010930,473205,807137661,10 ) for Aarch64 and MacOS, which requires us to disable alerting for those platforms. Sadly Perfherder doesn't allow to enable / disable alerting for specific platforms or tests whether on the suite nor sub-test level. Instead the results as pushed by the client have to be updated, by having `shouldAlert` set appropriately. It would be great if sheriffs could manage that via perfherder directly.