On Wed, 2007-10-03 at 14:15 +0100, sebb wrote: > The site updates are good. > > mvn package works for me on 1.4, correctly skipping the 1.5 stuff. > > However, mvn test causes an error on 1.4: > > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.apache.http.nio.TestAll > Tests run: 108, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.875 sec > <<< > FAILURE! > > Results : > Tests run: 108, Failures: 1, Errors: 0, Skipped: 0 > > I ran again with mvn test -e, and got the following: > > org.apache.maven.BuildFailureException: There are test failures. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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:324) > 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:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > > Not sure that helps much ...
Not really. Is this reproducible? Could you please check the content module-nio/target/surefire-reports/org.apache.http.nio.TestAll.txt? > This is on WinXP/SP2 (dual core) with > > java version "1.4.2_15" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02) > Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode) > > > mvn package is fine on Java 1.5 > java version "1.5.0_12" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) > Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) > > mvn test on 1.5 generates a stack trace (but is not counted as an error): > > java.nio.channels.AsynchronousCloseException > at > java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterr > uptibleChannel.java:185) > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236) > at > org.apache.http.impl.nio.reactor.SessionInputBufferImpl.fill(SessionI > nputBufferImpl.java:84) > at > org.apache.http.impl.nio.codecs.AbstractMessageParser.fillBuffer(Abst > ractMessageParser.java:97) > at org.apache.http.impl.nio.DefaultNHttpServerConnection.con[INFO] > sumeInput(De > faultNHttpServerConnection.java:110) > at > org.apache.http.impl.nio.DefaultServerIOEventDispatch.inputReady(Defa > ultServerIOEventDispatch.java:94) > at > org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor > .java:94) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(Abstr > actIOReactor.java:172) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(Abst > ractIOReactor.java:157) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIO > Reactor.java:128) > at > org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor. > java:69) > at > org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker. > run(AbstractMultiworkerIOReactor.java:281) > at java.lang.Thread.run(Thread.java:595) > Tests run: 108, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.281 sec > > Results : > Tests run: 108, Failures: 0, Errors: 0, Skipped: 0 > > If you want me to run more tests, just let me know. > This is sometimes happens, especially on multicore boxes under load, when JUnit force-shuts down the test HTTP server before it manages to shut itself down gracefully. > BTW, mvn seems to rebuild everything each time. > Not sure if that is a feature of Maven, or a setting that can be changed. > Hhmm. All seems OK here ---------------------------------------------------------------------------- [INFO] Building HttpCore (NIO extensions module) [INFO] task-segment: [test] [INFO] ---------------------------------------------------------------------------- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date Are you sure you are not running 'mvn clean test' or some such? Oleg > S/// > On 03/10/2007, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > > On Mon, 2007-10-01 at 17:19 +0100, sebb wrote: > > > On 01/10/2007, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > > > > ... > > > > > It would be nice if the Maven script could give a better error message > > > for that, rather than the rather cryptic: > > > > > > httpcomponents-core-4.0-alpha6-SNAPSHOT\module-nio\src\test\ > > > java\org\apache\http\impl\nio\codecs\TestLengthDelimitedDecoder.java:[93,12] > > > can > > > not resolve symbol > > > symbol : method read (java.nio.CharBuffer) > > > location: class java.io.InputStreamReader > > > > > > I don't know if this is possible in Maven, however. > > > > > > If not, a note in the text file would be useful - also how to > > > build/test the individual components in case someone does not want > > > them all. > > > > > > > Folks, > > > > Please find updated packages and the web site below > > > > Release notes: > > http://people.apache.org/~olegk/httpcore-4.0-alpha6-prerelease/RELEASE_NOTES.txt > > > > Packages: > > http://people.apache.org/~olegk/httpcore-4.0-alpha6-prerelease/packages/ > > > > Web site: > > http://people.apache.org/~olegk/httpcore-4.0-alpha6-prerelease/site/httpcomponents-core/ > > > > I believe I have addressed most of (if not all) concerns and > > suggestions. Maven now excludes Java 1.5 dependent modules when > > executed on an older JDK and shows a warning message when building > > packages. > > > > BUILDING.txt is now included with the src assembly. I am not much of a > > writer so do not expect a 'War and Peace' kind of things > > > > http://svn.apache.org/repos/asf/jakarta/httpcomponents/httpcore/trunk/BUILDING.txt > > > > 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]
