On Tue, Jul 9, 2013 at 10:50 AM, Carsten Ziegeler <cziege...@apache.org> wrote: > Yes, the tests pass - I thought maybe jenkins is scanning the log for an > ERROR message and finds this? >
That's a guess as good as any other. The previous build passed and it did not have this error message [1]. I've created [2] to track this. Robert [1]: https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/1722/consoleText [2]: https://issues.apache.org/jira/browse/SLING-2954 > Carsten > > > 2013/7/9 Robert Munteanu <romb...@apache.org> > >> On Tue, Jul 9, 2013 at 10:09 AM, Carsten Ziegeler <cziege...@apache.org> >> wrote: >> > I'm wondering why this is marked as failed? >> > >> > Is it because: >> > >> > 09.07.2013 06:43:12.354 *ERROR* [Jetty HTTP Service] >> > org.apache.felix.http.jetty Exception while initializing Jetty. >> > (java.net.BindException: Address already in use) >> > java.net.BindException: Address already in use >> > at sun.nio.ch.Net.bind(Native Method) >> > at >> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124) >> > at >> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) >> > at >> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216) >> > at >> org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315) >> > at >> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) >> > at org.mortbay.jetty.Server.doStart(Server.java:235) >> > at >> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) >> > at >> org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:164) >> > at >> org.apache.felix.http.jetty.internal.JettyService.startJetty(JettyService.java:115) >> > at >> org.apache.felix.http.jetty.internal.JettyService.run(JettyService.java:290) >> > at java.lang.Thread.run(Thread.java:662) >> > >> > As the test don't need the http service, this isn't really a problem. >> >> No, this isn't the cause. I ran the tests locally with port 8080 busy >> and the they passed, even though the same error was logged. >> >> I'm am really not sure why the build fails though, all tests pass. >> >> Robert >> > > > > -- > Carsten Ziegeler > cziege...@apache.org
