Has anyone considered allowing try pushes to run only specified directories of tests, and to allow incremental builds rather than clobbers on try? This would make try a heck of lot faster and resource-efficient, for those who are willing to accept less certain results.
On Wed, Nov 6, 2013 at 12:53 AM, L. David Baron <[email protected]> wrote: > I think it's worth tracking both the resource consumption rates and > backout rates of individual committers, because they're > substantially different, and if we want people working at the > correct optimum we should be giving opposite advice to different > committers. (I'm aware we track resource consumption on try at > [1].) I think some committers are too careful and overconsume > compute resources on try, and some are not careful enough and > overconsume resources (computer and human) on inbound. So we should > gather data so that we can give the correct advice to different > committers rather than giving blanket advice that's going to be > correct for some people and wrong for others. I agree with this. I'm a pedantic and cautious sort of person, so after seeing all sorts of scary warnings everywhere telling everyone not to push to inbound without a try run, I was careful to do a try run for the final version of every patch I wrote. This led to me being among the top try users (despite only working part-time). When someone pointed it out to me, I started using build-only or one-platform try pushes. If there's a big problem with people pushing untested code, it might be disproportionately due to a handful of individuals. On Wed, Nov 6, 2013 at 12:29 PM, Henri Sivonen <[email protected]> wrote: > Also, running the > tests locally is bad for developer productivity because some tests > want to have focus and whatnot, so your computer needs to be fully > devoted to running tests. xvfb-run works well to solve this on Linux, although it doesn't work perfectly with all test suites, and you can still only run one mochitest instance at once (even though it only uses one core) because it requires a specific port to be open. _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
