On Fri, Jul 1, 2016 at 1:02 PM, Karl Tomlinson <mozn...@karlt.net> wrote:
> William Lachance writes: > > > As part of a larger effort to improve the experience around > > debugging intermittents, I've been looking at reducing the time it > > takes for common "try" workloads for developers (so that > > e.g. retriggering a job to reproduce a failure can happen faster). > > > Also, accounts of specific try workloads of this type which are > > annoying/painful would be helpful. :) I think I have a rough idea > > of the particular type of try push I'm looking for (not pushed by > > release operations, at least one retrigger) but it would be great > > to get firsthand confirmation of that. > > One thing that might be helpful is enabling running only tests on > try with a designated build that has already been created. > > Often tests are modified to add logging, after which the same > build could be run with the new version of the test, thus saving > waiting for a build. > FWIW, there's a bug about this: https://bugzilla.mozilla.org/show_bug.cgi?id=1240644 - Xidorn _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
