I don't know why that would happen, but I can share with you my experience running the -all tests. I use a MacBookPro and on several occasions found the machine's CPU meter at 100% and barely responsive, running the tests very, very slowly. This was 1 or 2 months ago now. What we (Alex, Carol, and I) do is shutdown virus scanners and backup software when we run the tests. A normal "quick" run of a couple hundred tests always seemed fine to me. It was just the large test suites that involve compiling thousands of SWFs. I don't know if the machine tries to compile multiple SWFs at the same time or not; perhaps Alex or Carol can answer that.
Since the tests take a while to run, try to make sure all non-essential programs are stopped and let it go overnight. If other folks on this list are more machine-savvy than I, please weigh in with your suggestions. Thanks, Peter Ent Flex SDK Team Adobe Systems On 10/25/12 5:41 AM, "Jarosław Szczepankiewicz" <jszczepankiew...@gmail.com> wrote: >maybe running visualvm from jdk will give answer > >2012/10/25 Michael Schmalle <apa...@teotigraphix.com>: >> Hi, >> >> What is going on with the mustella test suite that would make all quad >>core >> cpus run at 100%? >> >> I know these tests are broad but, my computer got really unstable >>trying to >> run -all. >> >> Fact is I don't have time to wait an hour to see if I broke something >>when I >> am just doing edits in build files. >> >> BTW I had to kill all the java processes to get my computer not to >>crash. >> >> I'm running an HP Core Quad Q9300 2.5, 8GB Ram >> >> I have had this computer for a couple years and never had a problem like >> this only with some older programs. >> >> Mike >> >> -- >> Michael Schmalle - Teoti Graphix, LLC >> http://www.teotigraphix.com >> http://blog.teotigraphix.com >>
