You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Kevin Sutter <kw...@gmail.com> on 2006/07/06 23:26:50 UTC
testcase failures?
Hi,
I brought down the latest mavenized code for openjpa-lib and serp, and it
all builds cleanly. But, when the tests are run, I am hitting a few
failures. I'm wondering whether these are expected, or whether I have a
configuration or setup problem.
>From the output from maven, I am getting the following failures:
Running org.apache.openjpa.lib.xml.TestDocTypeReader
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.261 sec
<<< FAILURE!
Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
0 WARN [main] com.solarmetric.Runtime - memory: used: 3,600,112 total:
6,291,456 free: 2,691,344
0 WARN [main] com.solarmetric.Runtime - memory: used: 3,834,768 total:
6,291,456 free: 2,456,688
0 WARN [main] com.solarmetric.Runtime - memory: used: 3,943,032 total:
6,291,456 free: 2,348,424
0 WARN [main] com.solarmetric.Runtime - memory: used: 4,393,736 total:
6,291,456 free: 1,897,720
0 WARN [main] com.solarmetric.Runtime - memory: used: 4,451,384 total:
6,291,456 free: 1,840,072
0 WARN [main] com.solarmetric.Runtime - memory: used: 4,582,456 total:
6,291,456 free: 1,709,000
Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 0.07 sec <<<
FAILURE!
Running org.apache.openjpa.lib.xml.TestXMLWriter
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.1 sec <<<
FAILURE!
Running org.apache.openjpa.lib.util.TestPropertiesParser
Tests run: 13, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 0.261 sec
<<< FAILURE!
I'm willing to dive into these problems, but if these tests are expected to
run successfully, then I don't want to waste my time.
Thanks!
Kevin
Re: testcase failures?
Posted by Abe White <aw...@bea.com>.
> For example, this morning, I took a look at the TestXMLWriter
> test. When I
> run this individually within Eclipse, it shows an NPE when
> attempting to
> create a new InputStreamReader. From looking at the test, it looks
> like it
> is expecting the existence of some xml files for formatting and
> comparison
> -- raw-source.xml and formatted-result.xml. I can't find these
> files in the
> code drop and from the testcase, I can't quite figure out what the
> expected
> format should be.
Looks like stuff we forgot to include in the drop.
On a general note, I'd like to point out that there are certainly
many aspects of the dropped code that are in flux. You've already
seen that we haven't gone over the test failures yet. We also
included some in-flight features in the kernel code drop, so there is
code that hasn't been reviewed or tested thoroughly yet, and projects
like the concurrency stuff I mentioned a while ago that are only
partially-implemented. Finally, there are a few recent bits of
ugliness that we just haven't had time to clean up yet (as opposed to
the long-standing bits of ugliness that we've abandoned all hope of
fixing :).
Once we get the JDBC back-end contributed, hopefully we'll be able to
start fixing these things pretty quickly (assuming more of us have
gotten processed and have write access by then).
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Re: testcase failures?
Posted by Marc Prud'hommeaux <mp...@bea.com>.
Craig-
>> I'm getting more than a few failures. I don't know how to start
>> looking into them, as most of the error information seems to be
>> elided. Might be me, I just ran mvn -e install.
The Junit runner (called "surefire") outputs error information to the
target/surefire-reports/ directory of the module. E.g., the
TestConfigurationImpl failure can be seen in the following file:
openjpa-lib/target/surefire-reports/
org.apache.openjpa.lib.conf.test.TestConfigurationImpl.txt
I think there's a way to aggregate all those files together into a
single report (since it is tedious to have to browse through the
individual files), but I haven't tried it.
However, as Abe mentioned, I wouldn't worry too much about the test
failures right yet, since we are in a bit of flux, and some of the
files the tests rely on haven't been committed yet. For the time
being, you can skip the testing phase of the packaging process by
running:
mvn package -Dtest=false
On Jul 11, 2006, at 7:40 AM, Kevin Sutter wrote:
> Craig,
> It looks like the Junit tests for OpenJPA have minimal output.
> It's great
> when you run batch mode and everything works, but it's kind of pain
> when a
> test fails. I'm personally using Eclipse, so I just run each
> individual
> failing test within Eclipse. Still no console output, but it does
> provide
> an indication of the failure along with the stack trace so I can
> immediately
> get to the right area of the test.
>
> For example, this morning, I took a look at the TestXMLWriter
> test. When I
> run this individually within Eclipse, it shows an NPE when
> attempting to
> create a new InputStreamReader. From looking at the test, it looks
> like it
> is expecting the existence of some xml files for formatting and
> comparison
> -- raw-source.xml and formatted-result.xml. I can't find these
> files in the
> code drop and from the testcase, I can't quite figure out what the
> expected
> format should be.
>
> Anyway, that's how I am looking at the testcase results.
>
> Kevin
>
>
> On 7/10/06, Craig L Russell <Cr...@sun.com> wrote:
>>
>> Hi,
>>
>> I'm getting more than a few failures. I don't know how to start
>> looking into them, as most of the error information seems to be
>> elided. Might be me, I just ran mvn -e install.
>>
>> Anyone know how to get more info on these failures? If RTFM, could
>> you give me a reference? Mvn is a bit different from maven that I'm
>> used to...
>>
>> Craig
>>
>> ...
>> Running org.apache.openjpa.lib.xml.TestDocTypeReader
>> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.708
>> sec <<< FAILURE!
>> ...
>> Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
>> 0 WARN [main] com.solarmetric.Runtime - memory: used: 1,830,840
>> total: 2,957,312 free: 1,126,472
>> 0 WARN [main] com.solarmetric.Runtime - memory: used: 2,120,528
>> total: 2,957,312 free: 836,784
>> 0 WARN [main] com.solarmetric.Runtime - memory: used: 1,846,048
>> total: 2,957,312 free: 1,111,264
>> 0 WARN [main] com.solarmetric.Runtime - memory: used: 2,250,160
>> total: 2,957,312 free: 707,152
>> 0 WARN [main] com.solarmetric.Runtime - memory: used: 1,949,688
>> total: 2,957,312 free: 1,007,624
>> 0 WARN [main] com.solarmetric.Runtime - memory: used: 2,070,144
>> total: 2,957,312 free: 887,168
>> Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 0.247
>> sec <<< FAILURE!
>>
>> Running org.apache.openjpa.lib.xml.TestXMLWriter
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.239
>> sec <<< FAILURE!
>> ...
>> Results :
>> Tests run: 219, Failures: 2, Errors: 3, Skipped: 0
>>
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] There are test failures.
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] Trace
>> org.apache.maven.BuildFailureException: There are test failures.
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>> (DefaultLifecycleExecutor.java:555)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> fec
>> ycle(DefaultLifecycleExecutor.java:475)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
>> (DefaultLifecycleExecutor.java:454)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> dle
>> Failures(DefaultLifecycleExecutor.java:306)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> ts(
>> DefaultLifecycleExecutor.java:273)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
>> (DefaultLifecycleExecutor.java:140)
>> at org.apache.maven.DefaultMaven.doExecute
>> (DefaultMaven.java:
>> 322)
>> at org.apache.maven.DefaultMaven.execute
>> (DefaultMaven.java:115)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at org.codehaus.classworlds.Launcher.launchEnhanced
>> (Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:
>> 255)
>> at org.codehaus.classworlds.Launcher.mainWithExitCode
>> (Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by: org.apache.maven.plugin.MojoFailureException: There are
>> test failures.
>> at org.apache.maven.plugin.surefire.SurefirePlugin.execute
>> (SurefirePlugin.java:403)
>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo
>> (DefaultPluginManager.java:412)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>> (DefaultLifecycleExecutor.java:534)
>> ... 16 more
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] Total time: 30 seconds
>> [INFO] Finished at: Mon Jul 10 21:23:42 PDT 2006
>> [INFO] Final Memory: 5M/12M
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>>
>> On Jul 6, 2006, at 3:09 PM, Patrick Linskey wrote:
>>
>> > Yep, there are a few failures. These cropped up since Kodo 4.0 was
>> > released. They are not desirable, but are known. We didn't want to
>> > hold
>> > up putting code out there to get the tests running.
>> >
>> > Feel free to have a look at it.
>> >
>> > -Patrick
>> >
>> > --
>> > Patrick Linskey
>> > BEA Systems, Inc.
>> >
>> >> -----Original Message-----
>> >> From: Kevin Sutter [mailto:kwsutter@gmail.com]
>> >> Sent: Thursday, July 06, 2006 2:27 PM
>> >> To: open-jpa-dev@incubator.apache.org
>> >> Subject: testcase failures?
>> >>
>> >> Hi,
>> >> I brought down the latest mavenized code for openjpa-lib and
>> >> serp, and it all builds cleanly. But, when the tests are
>> >> run, I am hitting a few failures. I'm wondering whether
>> >> these are expected, or whether I have a configuration or
>> >> setup problem.
>> >>
>> >> From the output from maven, I am getting the following failures:
>> >>
>> >> Running org.apache.openjpa.lib.xml.TestDocTypeReader
>> >> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time
>> >> elapsed: 0.261 sec <<< FAILURE!
>> >>
>> >> Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
>> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> >> 3,600,112 total:
>> >> 6,291,456 free: 2,691,344
>> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> >> 3,834,768 total:
>> >> 6,291,456 free: 2,456,688
>> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> >> 3,943,032 total:
>> >> 6,291,456 free: 2,348,424
>> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> >> 4,393,736 total:
>> >> 6,291,456 free: 1,897,720
>> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> >> 4,451,384 total:
>> >> 6,291,456 free: 1,840,072
>> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> >> 4,582,456 total:
>> >> 6,291,456 free: 1,709,000
>> >> Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time
>> >> elapsed: 0.07 sec <<< FAILURE!
>> >>
>> >> Running org.apache.openjpa.lib.xml.TestXMLWriter
>> >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
>> >> elapsed: 0.1 sec <<< FAILURE!
>> >>
>> >> Running org.apache.openjpa.lib.util.TestPropertiesParser
>> >> Tests run: 13, Failures: 9, Errors: 0, Skipped: 0, Time
>> >> elapsed: 0.261 sec <<< FAILURE!
>> >>
>> >> I'm willing to dive into these problems, but if these tests
>> >> are expected to run successfully, then I don't want to waste my
>> time.
>> >>
>> >> Thanks!
>> >> Kevin
>> >>
>> >
>> _____________________________________________________________________
>> _
>> > _
>> > Notice: This email message, together with any attachments, may
>> > contain
>> > information of BEA Systems, Inc., its subsidiaries and
>> > affiliated
>> > entities, that may be confidential, proprietary, copyrighted
>> > and/or
>> > legally privileged, and is intended solely for the use of the
>> > individual
>> > or entity named in this message. If you are not the intended
>> > recipient,
>> > and have received this message in error, please immediately return
>> > this
>> > by email and then delete it.
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>>
>>
--
Marc Prud'hommeaux
BEA Systems, Inc.
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Re: testcase failures?
Posted by Kevin Sutter <kw...@gmail.com>.
Craig,
It looks like the Junit tests for OpenJPA have minimal output. It's great
when you run batch mode and everything works, but it's kind of pain when a
test fails. I'm personally using Eclipse, so I just run each individual
failing test within Eclipse. Still no console output, but it does provide
an indication of the failure along with the stack trace so I can immediately
get to the right area of the test.
For example, this morning, I took a look at the TestXMLWriter test. When I
run this individually within Eclipse, it shows an NPE when attempting to
create a new InputStreamReader. From looking at the test, it looks like it
is expecting the existence of some xml files for formatting and comparison
-- raw-source.xml and formatted-result.xml. I can't find these files in the
code drop and from the testcase, I can't quite figure out what the expected
format should be.
Anyway, that's how I am looking at the testcase results.
Kevin
On 7/10/06, Craig L Russell <Cr...@sun.com> wrote:
>
> Hi,
>
> I'm getting more than a few failures. I don't know how to start
> looking into them, as most of the error information seems to be
> elided. Might be me, I just ran mvn -e install.
>
> Anyone know how to get more info on these failures? If RTFM, could
> you give me a reference? Mvn is a bit different from maven that I'm
> used to...
>
> Craig
>
> ...
> Running org.apache.openjpa.lib.xml.TestDocTypeReader
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.708
> sec <<< FAILURE!
> ...
> Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
> 0 WARN [main] com.solarmetric.Runtime - memory: used: 1,830,840
> total: 2,957,312 free: 1,126,472
> 0 WARN [main] com.solarmetric.Runtime - memory: used: 2,120,528
> total: 2,957,312 free: 836,784
> 0 WARN [main] com.solarmetric.Runtime - memory: used: 1,846,048
> total: 2,957,312 free: 1,111,264
> 0 WARN [main] com.solarmetric.Runtime - memory: used: 2,250,160
> total: 2,957,312 free: 707,152
> 0 WARN [main] com.solarmetric.Runtime - memory: used: 1,949,688
> total: 2,957,312 free: 1,007,624
> 0 WARN [main] com.solarmetric.Runtime - memory: used: 2,070,144
> total: 2,957,312 free: 887,168
> Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 0.247
> sec <<< FAILURE!
>
> Running org.apache.openjpa.lib.xml.TestXMLWriter
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.239
> sec <<< FAILURE!
> ...
> Results :
> Tests run: 219, Failures: 2, Errors: 3, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: There are test failures.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (DefaultLifecycleExecutor.java:555)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
> ycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> Failures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
> 322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced
> (Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode
> (Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are
> test failures.
> at org.apache.maven.plugin.surefire.SurefirePlugin.execute
> (SurefirePlugin.java:403)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (DefaultLifecycleExecutor.java:534)
> ... 16 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 30 seconds
> [INFO] Finished at: Mon Jul 10 21:23:42 PDT 2006
> [INFO] Final Memory: 5M/12M
> [INFO]
> ------------------------------------------------------------------------
>
> On Jul 6, 2006, at 3:09 PM, Patrick Linskey wrote:
>
> > Yep, there are a few failures. These cropped up since Kodo 4.0 was
> > released. They are not desirable, but are known. We didn't want to
> > hold
> > up putting code out there to get the tests running.
> >
> > Feel free to have a look at it.
> >
> > -Patrick
> >
> > --
> > Patrick Linskey
> > BEA Systems, Inc.
> >
> >> -----Original Message-----
> >> From: Kevin Sutter [mailto:kwsutter@gmail.com]
> >> Sent: Thursday, July 06, 2006 2:27 PM
> >> To: open-jpa-dev@incubator.apache.org
> >> Subject: testcase failures?
> >>
> >> Hi,
> >> I brought down the latest mavenized code for openjpa-lib and
> >> serp, and it all builds cleanly. But, when the tests are
> >> run, I am hitting a few failures. I'm wondering whether
> >> these are expected, or whether I have a configuration or
> >> setup problem.
> >>
> >> From the output from maven, I am getting the following failures:
> >>
> >> Running org.apache.openjpa.lib.xml.TestDocTypeReader
> >> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time
> >> elapsed: 0.261 sec <<< FAILURE!
> >>
> >> Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> >> 3,600,112 total:
> >> 6,291,456 free: 2,691,344
> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> >> 3,834,768 total:
> >> 6,291,456 free: 2,456,688
> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> >> 3,943,032 total:
> >> 6,291,456 free: 2,348,424
> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> >> 4,393,736 total:
> >> 6,291,456 free: 1,897,720
> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> >> 4,451,384 total:
> >> 6,291,456 free: 1,840,072
> >> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> >> 4,582,456 total:
> >> 6,291,456 free: 1,709,000
> >> Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time
> >> elapsed: 0.07 sec <<< FAILURE!
> >>
> >> Running org.apache.openjpa.lib.xml.TestXMLWriter
> >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
> >> elapsed: 0.1 sec <<< FAILURE!
> >>
> >> Running org.apache.openjpa.lib.util.TestPropertiesParser
> >> Tests run: 13, Failures: 9, Errors: 0, Skipped: 0, Time
> >> elapsed: 0.261 sec <<< FAILURE!
> >>
> >> I'm willing to dive into these problems, but if these tests
> >> are expected to run successfully, then I don't want to waste my time.
> >>
> >> Thanks!
> >> Kevin
> >>
> > ______________________________________________________________________
> > _
> > Notice: This email message, together with any attachments, may
> > contain
> > information of BEA Systems, Inc., its subsidiaries and
> > affiliated
> > entities, that may be confidential, proprietary, copyrighted
> > and/or
> > legally privileged, and is intended solely for the use of the
> > individual
> > or entity named in this message. If you are not the intended
> > recipient,
> > and have received this message in error, please immediately return
> > this
> > by email and then delete it.
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
>
>
Re: testcase failures?
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi,
I'm getting more than a few failures. I don't know how to start
looking into them, as most of the error information seems to be
elided. Might be me, I just ran mvn -e install.
Anyone know how to get more info on these failures? If RTFM, could
you give me a reference? Mvn is a bit different from maven that I'm
used to...
Craig
...
Running org.apache.openjpa.lib.xml.TestDocTypeReader
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.708
sec <<< FAILURE!
...
Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
0 WARN [main] com.solarmetric.Runtime - memory: used: 1,830,840
total: 2,957,312 free: 1,126,472
0 WARN [main] com.solarmetric.Runtime - memory: used: 2,120,528
total: 2,957,312 free: 836,784
0 WARN [main] com.solarmetric.Runtime - memory: used: 1,846,048
total: 2,957,312 free: 1,111,264
0 WARN [main] com.solarmetric.Runtime - memory: used: 2,250,160
total: 2,957,312 free: 707,152
0 WARN [main] com.solarmetric.Runtime - memory: used: 1,949,688
total: 2,957,312 free: 1,007,624
0 WARN [main] com.solarmetric.Runtime - memory: used: 2,070,144
total: 2,957,312 free: 887,168
Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 0.247
sec <<< FAILURE!
Running org.apache.openjpa.lib.xml.TestXMLWriter
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.239
sec <<< FAILURE!
...
Results :
Tests run: 219, Failures: 2, Errors: 3, Skipped: 0
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] There are test failures.
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:555)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced
(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode
(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: There are
test failures.
at org.apache.maven.plugin.surefire.SurefirePlugin.execute
(SurefirePlugin.java:403)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:534)
... 16 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 30 seconds
[INFO] Finished at: Mon Jul 10 21:23:42 PDT 2006
[INFO] Final Memory: 5M/12M
[INFO]
------------------------------------------------------------------------
On Jul 6, 2006, at 3:09 PM, Patrick Linskey wrote:
> Yep, there are a few failures. These cropped up since Kodo 4.0 was
> released. They are not desirable, but are known. We didn't want to
> hold
> up putting code out there to get the tests running.
>
> Feel free to have a look at it.
>
> -Patrick
>
> --
> Patrick Linskey
> BEA Systems, Inc.
>
>> -----Original Message-----
>> From: Kevin Sutter [mailto:kwsutter@gmail.com]
>> Sent: Thursday, July 06, 2006 2:27 PM
>> To: open-jpa-dev@incubator.apache.org
>> Subject: testcase failures?
>>
>> Hi,
>> I brought down the latest mavenized code for openjpa-lib and
>> serp, and it all builds cleanly. But, when the tests are
>> run, I am hitting a few failures. I'm wondering whether
>> these are expected, or whether I have a configuration or
>> setup problem.
>>
>> From the output from maven, I am getting the following failures:
>>
>> Running org.apache.openjpa.lib.xml.TestDocTypeReader
>> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time
>> elapsed: 0.261 sec <<< FAILURE!
>>
>> Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
>> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> 3,600,112 total:
>> 6,291,456 free: 2,691,344
>> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> 3,834,768 total:
>> 6,291,456 free: 2,456,688
>> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> 3,943,032 total:
>> 6,291,456 free: 2,348,424
>> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> 4,393,736 total:
>> 6,291,456 free: 1,897,720
>> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> 4,451,384 total:
>> 6,291,456 free: 1,840,072
>> 0 WARN [main] com.solarmetric.Runtime - memory: used:
>> 4,582,456 total:
>> 6,291,456 free: 1,709,000
>> Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time
>> elapsed: 0.07 sec <<< FAILURE!
>>
>> Running org.apache.openjpa.lib.xml.TestXMLWriter
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
>> elapsed: 0.1 sec <<< FAILURE!
>>
>> Running org.apache.openjpa.lib.util.TestPropertiesParser
>> Tests run: 13, Failures: 9, Errors: 0, Skipped: 0, Time
>> elapsed: 0.261 sec <<< FAILURE!
>>
>> I'm willing to dive into these problems, but if these tests
>> are expected to run successfully, then I don't want to waste my time.
>>
>> Thanks!
>> Kevin
>>
> ______________________________________________________________________
> _
> Notice: This email message, together with any attachments, may
> contain
> information of BEA Systems, Inc., its subsidiaries and
> affiliated
> entities, that may be confidential, proprietary, copyrighted
> and/or
> legally privileged, and is intended solely for the use of the
> individual
> or entity named in this message. If you are not the intended
> recipient,
> and have received this message in error, please immediately return
> this
> by email and then delete it.
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
RE: testcase failures?
Posted by Patrick Linskey <pl...@bea.com>.
Yep, there are a few failures. These cropped up since Kodo 4.0 was
released. They are not desirable, but are known. We didn't want to hold
up putting code out there to get the tests running.
Feel free to have a look at it.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
> -----Original Message-----
> From: Kevin Sutter [mailto:kwsutter@gmail.com]
> Sent: Thursday, July 06, 2006 2:27 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: testcase failures?
>
> Hi,
> I brought down the latest mavenized code for openjpa-lib and
> serp, and it all builds cleanly. But, when the tests are
> run, I am hitting a few failures. I'm wondering whether
> these are expected, or whether I have a configuration or
> setup problem.
>
> From the output from maven, I am getting the following failures:
>
> Running org.apache.openjpa.lib.xml.TestDocTypeReader
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 0.261 sec <<< FAILURE!
>
> Running org.apache.openjpa.lib.conf.test.TestConfigurationImpl
> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> 3,600,112 total:
> 6,291,456 free: 2,691,344
> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> 3,834,768 total:
> 6,291,456 free: 2,456,688
> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> 3,943,032 total:
> 6,291,456 free: 2,348,424
> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> 4,393,736 total:
> 6,291,456 free: 1,897,720
> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> 4,451,384 total:
> 6,291,456 free: 1,840,072
> 0 WARN [main] com.solarmetric.Runtime - memory: used:
> 4,582,456 total:
> 6,291,456 free: 1,709,000
> Tests run: 7, Failures: 2, Errors: 1, Skipped: 0, Time
> elapsed: 0.07 sec <<< FAILURE!
>
> Running org.apache.openjpa.lib.xml.TestXMLWriter
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 0.1 sec <<< FAILURE!
>
> Running org.apache.openjpa.lib.util.TestPropertiesParser
> Tests run: 13, Failures: 9, Errors: 0, Skipped: 0, Time
> elapsed: 0.261 sec <<< FAILURE!
>
> I'm willing to dive into these problems, but if these tests
> are expected to run successfully, then I don't want to waste my time.
>
> Thanks!
> Kevin
>
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.