On Thu, Mar 12, 2015, at 08:50 PM, Robert O'Callahan wrote: > On Fri, Mar 13, 2015 at 12:34 PM, Seth Fowler <[email protected]> wrote:
> To work around these issues, I would like to have a dedicated machine > that > continuously downloads builds and runs tests under rr. Ideally it would > reenable tests that have been disabled-for-orange. When it finds > failures, > we would match failures to bugs and notify in the bug that an rr trace is > available. Developers could then ssh into the box to get a debugging > session. This should be reasonably easy to set up, especially if we start > by focusing on the simpler test suites and manually update bugs. Before we go buying a machine and sticking it under someone's desk (although let's not rule that out entirely!) I filed a bug[1] to see if we have any existing machines that are virtual machine hosts that have a usable CPU such that we could enable performance counters[2] and run rr in a VM there. Regardless of what hardware we wind up running it on, we'll still need to sort out the actual automation here. Historically we had people using a VMware record-and-replay setup on a physical machine in the MV office. AIUI that was entirely manual--someone would do a build, run the test harness with --run-until-failure, and let it churn until it hit a failure, at which point debugging would commence. Replicating this setup with rr seems pretty doable, but obviously a more automated setup would be preferable. The other question I have is: what percentage of our intermittent failures occur on Linux? If it's not that high then this is a lot of investment for minimal gain. -Ted 1. https://bugzilla.mozilla.org/show_bug.cgi?id=1142947 2 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2030221 _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
