On Sun, Feb 14, 2016 at 9:16 PM, Robert O'Callahan <rob...@ocallahan.org> wrote:
> Over the last few days we have had a lot of positive experiences > reproducing bugs with rr chaos mode. Kyle tells me that, in fact, he's been > able to reproduce every single bug he tried with enough machine time thrown > at it. > Of five or so, but yes. At this point the limiting factor is getting developers to actually debug > and fix recorded test failures. Anyone should be able to set up a VM on > their local machine, build Firefox, record some failures and fix them. For > best results, run just one test that's known intermittent, or possibly the > whole directory of tests if there might be inter-test dependencies. Use > --shuffle and --run-until-failure. The most convenient way to run rr with > chaos mode is probably to create a script rr-chaos that prepends the > --chaos option, and use --debugger rr-chaos. > You can generally pass --debugger=/path/to/rr --debugger-args="record -h" to mach to get things working. Lots of tests have been disabled for intermittency over the years. Now we > have the ability to fix (at least some of) them without much pain, it may > be worth revisiting them, though i don't know how to prioritize that. > FWIW, every failure that I've debugged to completion so far has been a bug in the test (although I have two fatal assertion bugs I'm working through that will obviously be flaws in Gecko). I think one of the things we really want to get a feeling for is how often we find actual bugs in the product. - Kyle _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
