directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niklas Therning (JIRA)" <>
Subject [jira] Resolved: (DIRMINA-159) Build of the project fails due to tests not passsing
Date Thu, 19 Jan 2006 20:41:43 GMT
     [ ]
Niklas Therning resolved DIRMINA-159:

    Resolution: Fixed

I've now changed every occurence of InetAddress.getLocalHost() to use "localhost" or similar.
I've also changed InetAddressEditorTest to only do lookups of external hosts if there is a
network connection. MINA shoud now build without a network connection and without the current
host's name resolving to an IP. I've verified this on my system.

I also had to downgrade easymockclassextension to 1.1 since 1.2 isn't in ibiblio and maven
fails if it can't connect to ibiblio. Maven tried to download the easymockclassextension 1.2
pom on every build. If network is up it will only display a warning and the build succeeds
but when network is down the build will always fail even if I have the JAR in my local repo.

Ersin, I really hope it works this time! :-)

> Build of the project fails due to tests not passsing
> ----------------------------------------------------
>          Key: DIRMINA-159
>          URL:
>      Project: Directory MINA
>         Type: Bug
>  Environment: Java. 1.5.0_06, Maven 2.0.1, Fedora Core 4
>     Reporter: Ersin Er
>     Assignee: Niklas Therning
>     Priority: Blocker
>      Fix For: 0.9.1

> The build of the project sometimes fail with the following messages:
> [surefire] Running org.apache.mina.transport.socket.nio.SocketTrafficControlTest
> [surefire] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.164 sec <<<<<<<<
> [surefire] Running org.apache.mina.transport.socket.nio.DatagramTrafficControlTest
> [surefire] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.146 sec <<<<<<<<
> However, this is not a certain case that happens all the time and when it happens, it
blocks the build of the whole directory project in trunk which is really bad.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message