On Tue, Jul 9, 2013 at 2:01 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 7/9/13 12:39 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > >On Tue, Jul 9, 2013 at 12:35 PM, Alex Harui <aha...@adobe.com> wrote: > > > >> So, now that we have a automated validation server thanks to Erik, and > >>all > >> tests are passing, someone is going to be the first one to break some > >> tests and have to revert out their changes. > >> > >> One way to reduce the chance it will be you is to try out your changes > >>on > >> the Mustella Patch Testing Server that I have running on a spare > >>computer > >> in my garage before you push your changes. It currently only knows how > >>to > >> test the main SDK: it doesn't run mobile or AIR tests. > >> > >> To use it, create a .patch file with your proposed changes, attach it to > >> an email and send it to mustellarun...@gmail.com. In theory it will > >>send > >> you an ack that it has received your patch and later send you a list of > >> failures or a list of tests that passed. It tries to run only the tests > >> that are affected by the set of files that changed, not the whole suite. > >> I'm sure it has bugs so email me if you've sent it something and it > >>hasn't > >> responded. > >> > >> The nice thing about the patch testing server is that you don't have to > >> revert out your changes if there are failures: the server cleans up > >>after > >> every run. And it only notified you and not the commits@ list if there > >> are failures. > >> > >> These two servers should help us keep the code base in working order, > >>but > >> remember, the only true "authority" is Erik's server since it runs all > >> tests on what is actually in the code base. > >> > >> -Alex > >> > > > >This is a great tool/service, Alex! Maybe you can fire up your free > >Windows Azure VM and put the patch testing server on that VM? That way, > >you can share the RDC details to the PMC private list so that we have a > >back up. > > Yeah, I'll get around to that someday. I haven't even ordered MSDN yet. > All of the .sh files are checked in and it only uses Mutt for email and > not Jenkins. > > I've been pondering whether a VM I get should run this patch tester or > help in running all tests in parallel. >
IMO, you should use your VM to maintain the patch server. I think having redundancy/backup of the patch server is more important. Hopefully other committers will chip in with their VMs for the parallel runs approach. > > FWIW, the other experiment I've been meaning to try but haven't found time > is to get a new laptop with an SSD and try mustella on it. I'm convinced > Mustella is disk-bound and would get a significant boost from an SSD. > > -Alex > Some articles I have been reading suggest that Azure is all SSD [1] Maybe we already are running at top speed. -Om [1] http://gigaom.com/2012/06/05/new-windows-azure-goes-all-ssd-to-one-up-amazon-in-the-cloud/ [2] http://www.nethosting.com/buzz/blog/microsoft-azure-cloud-service-updated-today-with-all-ssd-storage-and-a-new-api/
