It seems like try/tbpl could automatically detect new test files and run them N times. That way, the developer doesn't have to do it manually, so it is less "intimidating" and also less likely to be skipped by accident or forgotten.
Running under rr would be nice, but even without rr this seems like it would be a nice addition to our testing infrastructure. On Mon, Feb 15, 2016 at 11:59 PM, Axel Hecht <l...@mozilla.com> wrote: > On 16/02/16 03:15, Kyle Huey wrote: > >> Seems like a good thing to expect developers to do locally today. >> > > Two concerns: > > What's the successs criteria here? > > Also, speaking as an occasional code contributor, newcomers and folks like > me will probably give up on contributing patches earlier. > > Axel > > >> - Kyle >> >> On Mon, Feb 15, 2016 at 6:08 PM, Justin Dolske <dol...@mozilla.com> >> wrote: >> >> On 2/14/16 9:25 PM, Bobby Holley wrote: >>> >>> How far are we from being able to use cloud (rather than local) machine >>> >>>> time to produce a trace of an intermittently-failing bug? Some one-click >>>> procedure to produce a trace from a failure on treeherder seems like it >>>> would lower the activation energy significantly. >>>> >>>> >>> And with that... At some point, what about having all *new* tests be >>> battle-tested by X runs of rr-chaos testing? If it passes, it's allowed >>> to >>> run in the usual CI automation. If it fails, it's not (and you have a >>> handy >>> recording to debug). >>> >>> Justin >>> >>> _______________________________________________ >>> 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 > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
