2009/3/27 Steve Appling <[email protected]> > > > Adam Murdoch wrote: > >> >> >> Steve Appling wrote: >> >>> >>> >>> Adam Murdoch wrote: >>> >>>> Steve Appling wrote: >>>> >>>>> Adam Murdoch wrote: >>>>> >>>>>> All the CI builds are green, so the int tests are working somewhere at >>>>>> least. What does the test report say about these failures? >>>>>> >>>>> >>>>> I am having problems running unit tests now. >>>>> >>>>> gradlew test for the trunk results in: >>>>> >>>>> [ant:junit] Could not create the Java virtual machine. >>>>> java.io.FileNotFoundException: >>>>> C:\OpenSource\gradle\gradle-trunk\junitvmwatcher1 >>>>> 048259017.properties (The system cannot find the file specified) >>>>> at java.io.FileInputStream.open(Native Method) >>>>> ... >>>>> >>>>> This was building fine last week. I even tried getting a clean copy of >>>>> the head from svn, but no change. >>>>> >>>>> Anyone have an idea what might be causing this? >>>>> >>>>> >>>> There's an occasional OOM when running the unit tests, and one of the >>>> symptoms is the error message you saw. I've no idea what causes it, yet. It >>>> doesn't happen every time the unit tests run, just some times. >>>> >>>> Does the problem come and go if you run the unit tests a few times? >>>> >>>> >>> This happens every time now. >>> I went back through the revisions until it worked again. The problem >>> starts with revision 1275 (a change to increase the memory size and permgen >>> space for tests). >>> >>> >> Ok. Can you try reducing the max memory setting used for running the tests >> in build.gradle? >> >> > With the head revision, if I just reduce the MaxPermSize to 128m then both > unit tests and integration tests pass. At 256m I get the previously > mentioned error. >
I had set the permsize to 256m with max memory on 2g, I didn't pay attention to it when the max memory size was reduced again to 1g. This may also be the source of our occasional OOM. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
