It was systematic.

"was" : I can't run the test anymore, my crappy Dell just died 2 hours
ago. Bought a MBP instead...

On Thu, Nov 26, 2009 at 10:48 PM, Niklas Gustavsson
<[email protected]> wrote:
> On Thu, Nov 26, 2009 at 10:09 PM, Bernd Fondermann
> <[email protected]> wrote:
>> I can reproduce with a fresh trunk checkout and
>>  mvn -Dmaven.test.skip install
>> If I don't skip the tests, then build fails with unit test error.
>
> As Emmanuel described, excluding test running will not compile the
> tests and thus the test JAR can not be built.
>
> Would be good with some more details on the tests that fail. Which
> ones? Intermittent or reoccuring? Any output from the tests? Do they
> fail if you run them from somewhere else, like your IDE?
>
>>  mvn --version
>> gives
>>  Maven version: 2.0.9
>>  Java version: 1.6.0_15
>>  OS name: "mac os x" version: "10.6" arch: "i386" Family: "mac"
>
> Looks much like mine:
>
> mvn --version
> Maven version: 2.0.9
> Java version: 1.6.0_15
> OS name: "mac os x" version: "10.6.2" arch: "x86_64" Family: "mac"
>
> I tried to reproduce again:
> rm -rf /var/maven/repository/org/apache/vysper # clean out vysper from
> the local repository just to be sure
> svn co https://svn.apache.org/repos/asf/mina/sandbox/vysper/trunk vysper
> cd vysper
> mvn install
>
> Build succeeds (same thing in our Hudson builds, we do however wierdly
> enough have test failures on JDK 1.5, something I'm about to look into
> as soon as I can get JDK 1.5 installed on my laptop) . We do get some
> intermittent failures on some tests, something I was thinking of
> asking your assistance in tracking down. That's why I'm wondering if
> the test failures you get are intermittent.
>
> /niklas
>



-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Reply via email to