You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by Graham Leggett <mi...@sharp.fm> on 2007/03/19 23:23:04 UTC
Test failure on trunk
Hi all,
While trying to build trunk of continuum, I am getting the following
test failure on MacosX v10.4:
-------------------------------------------------------------------------------
Test set:
org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 255.852
sec <<<
FAILURE!
testWithDependencyChanges(org.apache.maven.continuum.buildcontroller.DefaultBuil
dControllerTest) Time elapsed: 79.372 sec <<< ERROR!
java.lang.OutOfMemoryError: Java heap space
Not sure exactly where the JVM should be given more memory, is this a
maven problem or a continuum problem?
Regards,
Graham
--
Re: Test failure on trunk
Posted by Marcelo Fukushima <ta...@gmail.com>.
im not sure but i think in order to change the amount of memory the
tests can use, you have to configure the surefire plugin - changing
the amount of memory maven uses dont take effect on tests (i think
they are ran on a separate jvm)
On 3/19/07, Emmanuel Venisse <em...@venisse.net> wrote:
> it's set in MAVEN_OPTS env var with -Xmx and -Xms java options, but if you don't know it, you probably use the default jvm options. You can try to it to something like that:
> MAVEN_OPTS=-Xmx256m
>
> If you don't want to patch Continuum, you can use a prebuilt snapshot: http://maven.zones.apache.org/~continuum/builds/trunk/
>
> Graham Leggett a écrit :
> > Emmanuel Venisse wrote:
> >
> >> how many memory is allocated to the build? Normally the default is
> >> enough.
> >
> > No idea - checked out a pristine copy of trunk as of an hour or two ago,
> > and did an mvn install.
> >
> > Is there somewhere where memory allocations are set, perhaps in a pom file?
> >
> > Regards,
> > Graham
> > --
>
>
--
[]'s
Marcelo Takeshi Fukushima
Re: Test failure on trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
it's set in MAVEN_OPTS env var with -Xmx and -Xms java options, but if you don't know it, you probably use the default jvm options. You can try to it to something like that:
MAVEN_OPTS=-Xmx256m
If you don't want to patch Continuum, you can use a prebuilt snapshot: http://maven.zones.apache.org/~continuum/builds/trunk/
Graham Leggett a écrit :
> Emmanuel Venisse wrote:
>
>> how many memory is allocated to the build? Normally the default is
>> enough.
>
> No idea - checked out a pristine copy of trunk as of an hour or two ago,
> and did an mvn install.
>
> Is there somewhere where memory allocations are set, perhaps in a pom file?
>
> Regards,
> Graham
> --
Re: Test failure on trunk
Posted by Andrew Williams <an...@handyande.co.uk>.
I assumed that there was a leak or something weird and that it would
get addressed.
I have certainly seen it compile and test fine without it before,
recently too, so I know it is possible...
Andy
On 22 Mar 2007, at 15:46, Thierry Lach wrote:
> Any reason why this couldn't just be added permanently?
>
> On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
>>
>> I sometimes get that problem too, when I see it I insert the
>> following into the <build> section of continuum's root pom.xml
>>
>> <plugins>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-surefire-plugin</artifactId>
>> <configuration>
>> <argLine>-Xmx512m</argLine>
>> </configuration>
>> </plugin>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-compiler-plugin</artifactId>
>> <configuration>
>> <fork>true</fork>
>> <meminitial>128m</meminitial>
>> <maxmem>512m</maxmem>
>> </configuration>
>> </plugin>
>> </plugins>
>>
>> Andy
>>
>> On 19 Mar 2007, at 22:59, Graham Leggett wrote:
>>
>> > Emmanuel Venisse wrote:
>> >
>> >> how many memory is allocated to the build? Normally the default is
>> >> enough.
>> >
>> > No idea - checked out a pristine copy of trunk as of an hour or two
>> > ago, and did an mvn install.
>> >
>> > Is there somewhere where memory allocations are set, perhaps in a
>> > pom file?
>> >
>> > Regards,
>> > Graham
>> > --
>>
>>
Re: Test failure on trunk
Posted by Graham Leggett <mi...@sharp.fm>.
Jesse McConnell wrote:
> most people I know just add the following to their environment variables
>
> MAVEN_OPTS=-Xmx512m
It shouldn't be necessary to have to patch your environment to work
around bugs in unit tests, if the tests need 512MB of RAM, then the
surefire plugin should be configured to allocate 512MB of RAM.
+1 to this:
>> > <plugin>
>> > <groupId>org.apache.maven.plugins</groupId>
>> > <artifactId>maven-surefire-plugin</artifactId>
>> > <configuration>
>> > <argLine>-Xmx512m</argLine>
>> > </configuration>
>> > </plugin>
Regards,
Graham
--
Re: Test failure on trunk
Posted by Thierry Lach <th...@gmail.com>.
Thanks.
On 3/29/07, Emmanuel Venisse <em...@venisse.net> wrote:
>
> I added the jvm memory option to the surefire plugin because now I have
> this pb too :(
>
> Emmanuel
>
> Thierry Lach a écrit :
> > I agree. I don't want to have to bump up my memory config for all
> projects
> > just because of one.
> >
> > On 3/23/07, Andrew Williams <an...@handyande.co.uk> wrote:
> >>
> >> I think that modifying your environment or installation options is a
> >> very bad idea,
> >> especially if you are striving for truly reproducible build results.
> >>
> >> Andy
> >>
> >> On 22 Mar 2007, at 16:29, Jesse McConnell wrote:
> >>
> >> > most people I know just add the following to their environment
> >> > variables
> >> >
> >> > MAVEN_OPTS=-Xmx512m
> >> >
> >> > jesse
> >> >
> >> > On 3/22/07, Thierry Lach <th...@gmail.com> wrote:
> >> >> Any reason why this couldn't just be added permanently?
> >> >>
> >> >> On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
> >> >> >
> >> >> > I sometimes get that problem too, when I see it I insert the
> >> >> > following into the <build> section of continuum's root pom.xml
> >> >> >
> >> >> > <plugins>
> >> >> > <plugin>
> >> >> > <groupId>org.apache.maven.plugins</groupId>
> >> >> > <artifactId>maven-surefire-plugin</artifactId>
> >> >> > <configuration>
> >> >> > <argLine>-Xmx512m</argLine>
> >> >> > </configuration>
> >> >> > </plugin>
> >> >> > <plugin>
> >> >> > <groupId>org.apache.maven.plugins</groupId>
> >> >> > <artifactId>maven-compiler-plugin</artifactId>
> >> >> > <configuration>
> >> >> > <fork>true</fork>
> >> >> > <meminitial>128m</meminitial>
> >> >> > <maxmem>512m</maxmem>
> >> >> > </configuration>
> >> >> > </plugin>
> >> >> > </plugins>
> >> >> >
> >> >> > Andy
> >> >> >
> >> >> > On 19 Mar 2007, at 22:59, Graham Leggett wrote:
> >> >> >
> >> >> > > Emmanuel Venisse wrote:
> >> >> > >
> >> >> > >> how many memory is allocated to the build? Normally the
> >> >> default is
> >> >> > >> enough.
> >> >> > >
> >> >> > > No idea - checked out a pristine copy of trunk as of an hour
> >> >> or two
> >> >> > > ago, and did an mvn install.
> >> >> > >
> >> >> > > Is there somewhere where memory allocations are set, perhaps in
> a
> >> >> > > pom file?
> >> >> > >
> >> >> > > Regards,
> >> >> > > Graham
> >> >> > > --
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> > --
> >> > jesse mcconnell
> >> > jesse.mcconnell@gmail.com
> >> >
> >>
> >>
> >
>
>
Re: Test failure on trunk
Posted by Christian Gruber <cg...@israfil.net>.
Yeah - I finally got it, so I'll test your update.
BTW, pretty sure others have mentioned this, but it's working nicely
on my MacOS X Tiger (10.4.9) laptop.
Christian.
On Mar 29, 2007, at 11:08 AM, Emmanuel Venisse wrote:
> I added the jvm memory option to the surefire plugin because now I
> have this pb too :(
>
> Emmanuel
>
> Thierry Lach a écrit :
>> I agree. I don't want to have to bump up my memory config for all
>> projects
>> just because of one.
>> On 3/23/07, Andrew Williams <an...@handyande.co.uk> wrote:
>>>
>>> I think that modifying your environment or installation options is a
>>> very bad idea,
>>> especially if you are striving for truly reproducible build results.
>>>
>>> Andy
>>>
>>> On 22 Mar 2007, at 16:29, Jesse McConnell wrote:
>>>
>>> > most people I know just add the following to their environment
>>> > variables
>>> >
>>> > MAVEN_OPTS=-Xmx512m
>>> >
>>> > jesse
>>> >
>>> > On 3/22/07, Thierry Lach <th...@gmail.com> wrote:
>>> >> Any reason why this couldn't just be added permanently?
>>> >>
>>> >> On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
>>> >> >
>>> >> > I sometimes get that problem too, when I see it I insert the
>>> >> > following into the <build> section of continuum's root pom.xml
>>> >> >
>>> >> > <plugins>
>>> >> > <plugin>
>>> >> > <groupId>org.apache.maven.plugins</groupId>
>>> >> > <artifactId>maven-surefire-plugin</artifactId>
>>> >> > <configuration>
>>> >> > <argLine>-Xmx512m</argLine>
>>> >> > </configuration>
>>> >> > </plugin>
>>> >> > <plugin>
>>> >> > <groupId>org.apache.maven.plugins</groupId>
>>> >> > <artifactId>maven-compiler-plugin</artifactId>
>>> >> > <configuration>
>>> >> > <fork>true</fork>
>>> >> > <meminitial>128m</meminitial>
>>> >> > <maxmem>512m</maxmem>
>>> >> > </configuration>
>>> >> > </plugin>
>>> >> > </plugins>
>>> >> >
>>> >> > Andy
>>> >> >
>>> >> > On 19 Mar 2007, at 22:59, Graham Leggett wrote:
>>> >> >
>>> >> > > Emmanuel Venisse wrote:
>>> >> > >
>>> >> > >> how many memory is allocated to the build? Normally the
>>> >> default is
>>> >> > >> enough.
>>> >> > >
>>> >> > > No idea - checked out a pristine copy of trunk as of an hour
>>> >> or two
>>> >> > > ago, and did an mvn install.
>>> >> > >
>>> >> > > Is there somewhere where memory allocations are set,
>>> perhaps in a
>>> >> > > pom file?
>>> >> > >
>>> >> > > Regards,
>>> >> > > Graham
>>> >> > > --
>>> >> >
>>> >> >
>>> >>
>>> >
>>> >
>>> > --
>>> > jesse mcconnell
>>> > jesse.mcconnell@gmail.com
>>> >
>>>
>>>
>
christian gruber + cgruber@israfil.net + bus 905.640.1119 + mob
416.998.6023
process coach and architect + ISRÁFÍL CONSULTING SERVICES
Re: Test failure on trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
I added the jvm memory option to the surefire plugin because now I have this pb too :(
Emmanuel
Thierry Lach a écrit :
> I agree. I don't want to have to bump up my memory config for all projects
> just because of one.
>
> On 3/23/07, Andrew Williams <an...@handyande.co.uk> wrote:
>>
>> I think that modifying your environment or installation options is a
>> very bad idea,
>> especially if you are striving for truly reproducible build results.
>>
>> Andy
>>
>> On 22 Mar 2007, at 16:29, Jesse McConnell wrote:
>>
>> > most people I know just add the following to their environment
>> > variables
>> >
>> > MAVEN_OPTS=-Xmx512m
>> >
>> > jesse
>> >
>> > On 3/22/07, Thierry Lach <th...@gmail.com> wrote:
>> >> Any reason why this couldn't just be added permanently?
>> >>
>> >> On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
>> >> >
>> >> > I sometimes get that problem too, when I see it I insert the
>> >> > following into the <build> section of continuum's root pom.xml
>> >> >
>> >> > <plugins>
>> >> > <plugin>
>> >> > <groupId>org.apache.maven.plugins</groupId>
>> >> > <artifactId>maven-surefire-plugin</artifactId>
>> >> > <configuration>
>> >> > <argLine>-Xmx512m</argLine>
>> >> > </configuration>
>> >> > </plugin>
>> >> > <plugin>
>> >> > <groupId>org.apache.maven.plugins</groupId>
>> >> > <artifactId>maven-compiler-plugin</artifactId>
>> >> > <configuration>
>> >> > <fork>true</fork>
>> >> > <meminitial>128m</meminitial>
>> >> > <maxmem>512m</maxmem>
>> >> > </configuration>
>> >> > </plugin>
>> >> > </plugins>
>> >> >
>> >> > Andy
>> >> >
>> >> > On 19 Mar 2007, at 22:59, Graham Leggett wrote:
>> >> >
>> >> > > Emmanuel Venisse wrote:
>> >> > >
>> >> > >> how many memory is allocated to the build? Normally the
>> >> default is
>> >> > >> enough.
>> >> > >
>> >> > > No idea - checked out a pristine copy of trunk as of an hour
>> >> or two
>> >> > > ago, and did an mvn install.
>> >> > >
>> >> > > Is there somewhere where memory allocations are set, perhaps in a
>> >> > > pom file?
>> >> > >
>> >> > > Regards,
>> >> > > Graham
>> >> > > --
>> >> >
>> >> >
>> >>
>> >
>> >
>> > --
>> > jesse mcconnell
>> > jesse.mcconnell@gmail.com
>> >
>>
>>
>
Re: Test failure on trunk
Posted by Thierry Lach <th...@gmail.com>.
I agree. I don't want to have to bump up my memory config for all projects
just because of one.
On 3/23/07, Andrew Williams <an...@handyande.co.uk> wrote:
>
> I think that modifying your environment or installation options is a
> very bad idea,
> especially if you are striving for truly reproducible build results.
>
> Andy
>
> On 22 Mar 2007, at 16:29, Jesse McConnell wrote:
>
> > most people I know just add the following to their environment
> > variables
> >
> > MAVEN_OPTS=-Xmx512m
> >
> > jesse
> >
> > On 3/22/07, Thierry Lach <th...@gmail.com> wrote:
> >> Any reason why this couldn't just be added permanently?
> >>
> >> On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
> >> >
> >> > I sometimes get that problem too, when I see it I insert the
> >> > following into the <build> section of continuum's root pom.xml
> >> >
> >> > <plugins>
> >> > <plugin>
> >> > <groupId>org.apache.maven.plugins</groupId>
> >> > <artifactId>maven-surefire-plugin</artifactId>
> >> > <configuration>
> >> > <argLine>-Xmx512m</argLine>
> >> > </configuration>
> >> > </plugin>
> >> > <plugin>
> >> > <groupId>org.apache.maven.plugins</groupId>
> >> > <artifactId>maven-compiler-plugin</artifactId>
> >> > <configuration>
> >> > <fork>true</fork>
> >> > <meminitial>128m</meminitial>
> >> > <maxmem>512m</maxmem>
> >> > </configuration>
> >> > </plugin>
> >> > </plugins>
> >> >
> >> > Andy
> >> >
> >> > On 19 Mar 2007, at 22:59, Graham Leggett wrote:
> >> >
> >> > > Emmanuel Venisse wrote:
> >> > >
> >> > >> how many memory is allocated to the build? Normally the
> >> default is
> >> > >> enough.
> >> > >
> >> > > No idea - checked out a pristine copy of trunk as of an hour
> >> or two
> >> > > ago, and did an mvn install.
> >> > >
> >> > > Is there somewhere where memory allocations are set, perhaps in a
> >> > > pom file?
> >> > >
> >> > > Regards,
> >> > > Graham
> >> > > --
> >> >
> >> >
> >>
> >
> >
> > --
> > jesse mcconnell
> > jesse.mcconnell@gmail.com
> >
>
>
Re: Test failure on trunk
Posted by Andrew Williams <an...@handyande.co.uk>.
I think that modifying your environment or installation options is a
very bad idea,
especially if you are striving for truly reproducible build results.
Andy
On 22 Mar 2007, at 16:29, Jesse McConnell wrote:
> most people I know just add the following to their environment
> variables
>
> MAVEN_OPTS=-Xmx512m
>
> jesse
>
> On 3/22/07, Thierry Lach <th...@gmail.com> wrote:
>> Any reason why this couldn't just be added permanently?
>>
>> On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
>> >
>> > I sometimes get that problem too, when I see it I insert the
>> > following into the <build> section of continuum's root pom.xml
>> >
>> > <plugins>
>> > <plugin>
>> > <groupId>org.apache.maven.plugins</groupId>
>> > <artifactId>maven-surefire-plugin</artifactId>
>> > <configuration>
>> > <argLine>-Xmx512m</argLine>
>> > </configuration>
>> > </plugin>
>> > <plugin>
>> > <groupId>org.apache.maven.plugins</groupId>
>> > <artifactId>maven-compiler-plugin</artifactId>
>> > <configuration>
>> > <fork>true</fork>
>> > <meminitial>128m</meminitial>
>> > <maxmem>512m</maxmem>
>> > </configuration>
>> > </plugin>
>> > </plugins>
>> >
>> > Andy
>> >
>> > On 19 Mar 2007, at 22:59, Graham Leggett wrote:
>> >
>> > > Emmanuel Venisse wrote:
>> > >
>> > >> how many memory is allocated to the build? Normally the
>> default is
>> > >> enough.
>> > >
>> > > No idea - checked out a pristine copy of trunk as of an hour
>> or two
>> > > ago, and did an mvn install.
>> > >
>> > > Is there somewhere where memory allocations are set, perhaps in a
>> > > pom file?
>> > >
>> > > Regards,
>> > > Graham
>> > > --
>> >
>> >
>>
>
>
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
>
Re: Test failure on trunk
Posted by Jesse McConnell <je...@gmail.com>.
most people I know just add the following to their environment variables
MAVEN_OPTS=-Xmx512m
jesse
On 3/22/07, Thierry Lach <th...@gmail.com> wrote:
> Any reason why this couldn't just be added permanently?
>
> On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
> >
> > I sometimes get that problem too, when I see it I insert the
> > following into the <build> section of continuum's root pom.xml
> >
> > <plugins>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-surefire-plugin</artifactId>
> > <configuration>
> > <argLine>-Xmx512m</argLine>
> > </configuration>
> > </plugin>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-compiler-plugin</artifactId>
> > <configuration>
> > <fork>true</fork>
> > <meminitial>128m</meminitial>
> > <maxmem>512m</maxmem>
> > </configuration>
> > </plugin>
> > </plugins>
> >
> > Andy
> >
> > On 19 Mar 2007, at 22:59, Graham Leggett wrote:
> >
> > > Emmanuel Venisse wrote:
> > >
> > >> how many memory is allocated to the build? Normally the default is
> > >> enough.
> > >
> > > No idea - checked out a pristine copy of trunk as of an hour or two
> > > ago, and did an mvn install.
> > >
> > > Is there somewhere where memory allocations are set, perhaps in a
> > > pom file?
> > >
> > > Regards,
> > > Graham
> > > --
> >
> >
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
Re: Test failure on trunk
Posted by Thierry Lach <th...@gmail.com>.
Any reason why this couldn't just be added permanently?
On 3/22/07, Andrew Williams <an...@handyande.co.uk> wrote:
>
> I sometimes get that problem too, when I see it I insert the
> following into the <build> section of continuum's root pom.xml
>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <argLine>-Xmx512m</argLine>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <fork>true</fork>
> <meminitial>128m</meminitial>
> <maxmem>512m</maxmem>
> </configuration>
> </plugin>
> </plugins>
>
> Andy
>
> On 19 Mar 2007, at 22:59, Graham Leggett wrote:
>
> > Emmanuel Venisse wrote:
> >
> >> how many memory is allocated to the build? Normally the default is
> >> enough.
> >
> > No idea - checked out a pristine copy of trunk as of an hour or two
> > ago, and did an mvn install.
> >
> > Is there somewhere where memory allocations are set, perhaps in a
> > pom file?
> >
> > Regards,
> > Graham
> > --
>
>
Re: Test failure on trunk
Posted by Andrew Williams <an...@handyande.co.uk>.
I sometimes get that problem too, when I see it I insert the
following into the <build> section of continuum's root pom.xml
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<argLine>-Xmx512m</argLine>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<fork>true</fork>
<meminitial>128m</meminitial>
<maxmem>512m</maxmem>
</configuration>
</plugin>
</plugins>
Andy
On 19 Mar 2007, at 22:59, Graham Leggett wrote:
> Emmanuel Venisse wrote:
>
>> how many memory is allocated to the build? Normally the default is
>> enough.
>
> No idea - checked out a pristine copy of trunk as of an hour or two
> ago, and did an mvn install.
>
> Is there somewhere where memory allocations are set, perhaps in a
> pom file?
>
> Regards,
> Graham
> --
Re: Test failure on trunk
Posted by Graham Leggett <mi...@sharp.fm>.
Emmanuel Venisse wrote:
> how many memory is allocated to the build? Normally the default is enough.
No idea - checked out a pristine copy of trunk as of an hour or two ago,
and did an mvn install.
Is there somewhere where memory allocations are set, perhaps in a pom file?
Regards,
Graham
--
Re: Test failure on trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
how many memory is allocated to the build? Normally the default is enough.
Graham Leggett a écrit :
> Emmanuel Venisse wrote:
>
>> jdk version?
>
> Latest MacOSX version, jdk v1.5.0_07-164.
>
> Regards,
> Graham
> --
Re: Test failure on trunk
Posted by Graham Leggett <mi...@sharp.fm>.
Emmanuel Venisse wrote:
> jdk version?
Latest MacOSX version, jdk v1.5.0_07-164.
Regards,
Graham
--
RE: Test failure on trunk
Posted by diroussel <na...@diroussel.xsmail.com>.
If you need to get a working build you can get one of the pre-build ones...
http://www.nabble.com/-continuum-build-trunk---SUCCESS---update--Sat-Mar-17-05%3A00%3A00-GMT-2007-tf3418114s177.html
Brian E. Fox wrote:
>
> I'm also getting plenty of test failures on trunk. I followed the
> instructions in readme.txt in continuum-trunk root to get the right sun
> jars into my repo. I'm building on windows with jdk 1.4.2_12. I seem to
> run into this every time I try to grab the software and build it. My
> continuum 1.0.3 installation is a mess right now and I need to get
> something working soon so I'm hoping to get onto 1.1.
>
> -------------------------------------------------------------------------------
> Test set:
> org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 50.421 sec
> <<< FAILURE!
> testWithDependencyChanges(org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest)
> Time elapsed: 8.188 sec <<< ERROR!
> javax.jdo.JDOFatalInternalException: Unexpected exception caught.
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:549)
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:478)
> at org.jpox.SchemaTool.createSchemaTables(SchemaTool.java:303)
> at org.apache.maven.continuum.AbstractContinuumTest.getStore(Abs
>
>
> -------------------------------------------------------------------------------
> Test set:
> org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest
> -------------------------------------------------------------------------------
> Tests run: 6, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 30.281 sec
> <<< FAILURE!
> testCreateProjectsWithModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest)
> Time elapsed: 4.39 sec <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<1> but was:<2>
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.failNotEquals(Assert.java:282)
> at junit.framework.Assert.assertEquals(Assert.java:64)
> at junit.framework.Assert.assertEquals(Assert.java:201)
> at junit.framework.Assert.assertEquals(Assert.java:207)
> at
> org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectsWithModules(MavenTwoContinuumProjectBuilderTest.java:193)
> at
>
> ---------------
> testCreateProjectsWithModuleswithParentPomIsntPomXml(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest)
> Time elapsed: 4.219 sec <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<1> but was:<2>
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.failNotEquals(Assert.java:282)
> at junit.framework.Assert.assertEquals(Assert.java:64)
> at junit.framework.Assert.assertEquals(Assert.java:201)
> at junit.framework.Assert.assertEquals(Assert.java:207)
> at
> org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectsWithModuleswithParentPomIsntPomXml(MavenTwoContinuumProjectBuilderTest.java:287)
> at
>
> --------------------
> testCreateProjectWithoutModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest)
> Time elapsed: 3.734 sec <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.failNotEquals(Assert.java:282)
> at junit.framework.Assert.assertEquals(Assert.java:64)
> at junit.framework.Assert.assertEquals(Assert.java:201)
> at junit.framework.Assert.assertEquals(Assert.java:207)
> at
> org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectWithoutModules(MavenTwoContinuumProjectBuilderTest.java:377)
> at
>
>
> -----Original Message-----
> From: Emmanuel Venisse [mailto:emmanuel@venisse.net]
> Sent: Monday, March 19, 2007 6:34 PM
> To: continuum-dev@maven.apache.org
> Subject: Re: Test failure on trunk
>
> jdk version?
>
> Graham Leggett a écrit :
>> Hi all,
>>
>> While trying to build trunk of continuum, I am getting the following
>> test failure on MacosX v10.4:
>>
>> -------------------------------------------------------------------------------
>>
>> Test set:
>> org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
>> -------------------------------------------------------------------------------
>>
>> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 255.852
>> sec <<<
>> FAILURE!
>> testWithDependencyChanges(org.apache.maven.continuum.buildcontroller.DefaultBuil
>>
>> dControllerTest) Time elapsed: 79.372 sec <<< ERROR!
>> java.lang.OutOfMemoryError: Java heap space
>>
>> Not sure exactly where the JVM should be given more memory, is this a
>> maven problem or a continuum problem?
>>
>> Regards,
>> Graham
>> --
>
>
>
--
View this message in context: http://www.nabble.com/Test-failure-on-trunk-tf3430142.html#a9636039
Sent from the Continuum - Dev mailing list archive at Nabble.com.
RE: Test failure on trunk
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I'm also getting plenty of test failures on trunk. I followed the instructions in readme.txt in continuum-trunk root to get the right sun jars into my repo. I'm building on windows with jdk 1.4.2_12. I seem to run into this every time I try to grab the software and build it. My continuum 1.0.3 installation is a mess right now and I need to get something working soon so I'm hoping to get onto 1.1.
-------------------------------------------------------------------------------
Test set: org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 50.421 sec <<< FAILURE!
testWithDependencyChanges(org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest) Time elapsed: 8.188 sec <<< ERROR!
javax.jdo.JDOFatalInternalException: Unexpected exception caught.
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:549)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:478)
at org.jpox.SchemaTool.createSchemaTables(SchemaTool.java:303)
at org.apache.maven.continuum.AbstractContinuumTest.getStore(Abs
-------------------------------------------------------------------------------
Test set: org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest
-------------------------------------------------------------------------------
Tests run: 6, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 30.281 sec <<< FAILURE!
testCreateProjectsWithModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest) Time elapsed: 4.39 sec <<< FAILURE!
junit.framework.AssertionFailedError: expected:<1> but was:<2>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:201)
at junit.framework.Assert.assertEquals(Assert.java:207)
at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectsWithModules(MavenTwoContinuumProjectBuilderTest.java:193)
at
---------------
testCreateProjectsWithModuleswithParentPomIsntPomXml(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest) Time elapsed: 4.219 sec <<< FAILURE!
junit.framework.AssertionFailedError: expected:<1> but was:<2>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:201)
at junit.framework.Assert.assertEquals(Assert.java:207)
at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectsWithModuleswithParentPomIsntPomXml(MavenTwoContinuumProjectBuilderTest.java:287)
at
--------------------
testCreateProjectWithoutModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest) Time elapsed: 3.734 sec <<< FAILURE!
junit.framework.AssertionFailedError: expected:<0> but was:<1>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:201)
at junit.framework.Assert.assertEquals(Assert.java:207)
at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectWithoutModules(MavenTwoContinuumProjectBuilderTest.java:377)
at
-----Original Message-----
From: Emmanuel Venisse [mailto:emmanuel@venisse.net]
Sent: Monday, March 19, 2007 6:34 PM
To: continuum-dev@maven.apache.org
Subject: Re: Test failure on trunk
jdk version?
Graham Leggett a écrit :
> Hi all,
>
> While trying to build trunk of continuum, I am getting the following
> test failure on MacosX v10.4:
>
> -------------------------------------------------------------------------------
>
> Test set:
> org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
> -------------------------------------------------------------------------------
>
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 255.852
> sec <<<
> FAILURE!
> testWithDependencyChanges(org.apache.maven.continuum.buildcontroller.DefaultBuil
>
> dControllerTest) Time elapsed: 79.372 sec <<< ERROR!
> java.lang.OutOfMemoryError: Java heap space
>
> Not sure exactly where the JVM should be given more memory, is this a
> maven problem or a continuum problem?
>
> Regards,
> Graham
> --
Re: Test failure on trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
jdk version?
Graham Leggett a écrit :
> Hi all,
>
> While trying to build trunk of continuum, I am getting the following
> test failure on MacosX v10.4:
>
> -------------------------------------------------------------------------------
>
> Test set:
> org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
> -------------------------------------------------------------------------------
>
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 255.852
> sec <<<
> FAILURE!
> testWithDependencyChanges(org.apache.maven.continuum.buildcontroller.DefaultBuil
>
> dControllerTest) Time elapsed: 79.372 sec <<< ERROR!
> java.lang.OutOfMemoryError: Java heap space
>
> Not sure exactly where the JVM should be given more memory, is this a
> maven problem or a continuum problem?
>
> Regards,
> Graham
> --
Re: Test failure on trunk
Posted by diroussel <na...@diroussel.xsmail.com>.
You don't say which svn revision you are on. Good practice to always mention
it as trunk is a moving target.
I also got this build error (or similar OOM) on MacOS 10.4, but I updated
the next day and rebuilt and the problem went away. So it wasn't my
environment but the tests.
Thanks
David
Graham Leggett wrote:
>
> Hi all,
>
> While trying to build trunk of continuum, I am getting the following
> test failure on MacosX v10.4:
>
> -------------------------------------------------------------------------------
> Test set:
> org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 255.852
> sec <<<
> FAILURE!
> testWithDependencyChanges(org.apache.maven.continuum.buildcontroller.DefaultBuil
> dControllerTest) Time elapsed: 79.372 sec <<< ERROR!
> java.lang.OutOfMemoryError: Java heap space
>
> Not sure exactly where the JVM should be given more memory, is this a
> maven problem or a continuum problem?
>
> Regards,
> Graham
> --
>
>
>
--
View this message in context: http://www.nabble.com/Test-failure-on-trunk-tf3430142.html#a9636080
Sent from the Continuum - Dev mailing list archive at Nabble.com.