Ran mvn test, got the following stacktrace:

Running org.apache.http.nio.TestAll
org.apache.http.nio.reactor.IOReactorException: Failure accepting connection
        at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvent(DefaultListeningIOReactor.java:103)
        at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvents(DefaultListeningIOReactor.java:84)
        at 
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:158)
        at 
org.apache.http.impl.nio.reactor.TestDefaultListeningIOReactor$1.run(TestDefaultListeningIOReactor.java:112)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.nio.channels.ClosedChannelException
        at 
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:130)
        at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvent(DefaultListeningIOReactor.java:100)
        ... 4 more
Tests run: 97, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.813 sec

For some reason this is not recorded as a failure or error ...

Results :
Tests run: 97, Failures: 0, Errors: 0, Skipped: 0

The surefire report shows success:

-------------------------------------------------------------------------------
Test set: org.apache.http.nio.TestAll
-------------------------------------------------------------------------------
Tests run: 97, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.829 sec



==================



When I ran mvn test again, I got this:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.http.nio.TestAll
org.apache.http.nio.reactor.IOReactorException: Failure accepting connection
        at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvent(DefaultListeningIOReactor.java:103)
        at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvents(DefaultListeningIOReactor.java:84)
        at 
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:158)
        at 
org.apache.http.impl.nio.reactor.TestDefaultListeningIOReactor$1.run(TestDefaultListeningIOReactor.java:112)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.nio.channels.ClosedChannelException
        at 
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:130)
        at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvent(DefaultListeningIOReactor.java:100)
        ... 4 more
Tests run: 97, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
11.782 sec <<< FAILURE!

Results :
Tests run: 97, Failures: 1, Errors: 0, Skipped: 0

with the surefire report:

-------------------------------------------------------------------------------
Test set: org.apache.http.nio.TestAll
-------------------------------------------------------------------------------
Tests run: 97, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
11.782 sec <<< FAILURE!
testEndpointUpAndDown(org.apache.http.impl.nio.reactor.TestDefaultListeningIOReactor)
 Time elapsed: 0.078 sec  <<< FAILURE!
junit.framework.AssertionFailedError: expected:<1> but was:<0>
        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.http.impl.nio.reactor.TestDefaultListeningIOReactor.testEndpointUpAndDown(TestDefaultListeningIOReactor.java:140)


======

Repeating "mvn test" shows the same Failure.

Odd.

The failures look rather similar - why should the first one be ignored?
Perhaps a bug in Maven or Surefire.

If I then run "mvn clean", then "mvn test" the stacktrace appears, but
it is not treated as a failure, even if I run "mvn test" several times
without an intervening clean.

Very odd.

Tried running "mvn test" in a fresh source tree:
- first time, no stack trace at all
- second and 3rd time, stack trace and failure recorded.
- mvn clean, then mvn test: stack trace and failure recorded.

The stacktrace seems to be repeatable now ... anything I can do to
debug it further?

On 16/01/2008, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
> Sebastian et al
>
> I fixed the problem with the assembly descriptors. Packages now seem all
> right. Please review.
>
> Oleg
>
>
> On Tue, 2008-01-15 at 11:32 +0100, Oleg Kalnichevski wrote:
> > Folks,
> >
> > Please take a few minutes to review the release notes and release
> > packages. If I hear no complaints, I'll go ahead with tagging the
> > release in SVN and building the official release artifacts.
> >
> > Feel free to add more stuff to the release notes as this is a very
> > important milestone for us.
> >
> > Release notes:
> > http://people.apache.org/~olegk/httpcore-4.0-beta1-preview/RELEASE_NOTES.txt
> >
> > Packages:
> > http://people.apache.org/~olegk/httpcore-4.0-beta1-preview/packages/
> >
> > Cheers
> >
> > Oleg
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to