The general problem as I see it is that talos try doesn't go orange if there's a regression (because we detect regressions over time), and checking the results against a baseline revision is kind of a pain, even with talos-compare. So I think most developers ignore it, and those who have the gumption to compare all those numbers can probably be bothered to explicitly write in the platforms they want.
On Wed, Oct 3, 2012 at 12:13 AM, Karl Tomlinson <mozn...@karlt.net> wrote: > Ehsan Akhgari writes: > > > Over in bug 796087, I'm proposing for us to remove the -t all try server > > flag. The rationale is that the set of Talos tests vary greatly and most > > of the people who test performance are only interested in a subset of > Talos > > tests. > > Frequently enough people change code that I would expect could > change any talos results except perhaps dromaeojs. > > I'm wondering whether there is a smaller subset that should be > considered. > > Are there other suites that should not be affected by graphics > code changes, for example? > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
