Re: Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1723
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. Carsten 2013/7/9 Apache Jenkins Server jenk...@builds.apache.org See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/1723/changes Changes: [cziegeler] SLING-2950 : Disabling the distribution flag takes only effect after bundle restart -- [...truncated 9463 lines...] 09.07.2013 06:49:26.718 *INFO* [main] org.apache.sling.event.impl.jobs.JobConsumerManager Updating property provider with: / 09.07.2013 06:49:26.718 *INFO* [main] org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event TopologyEvent [type=PROPERTIES_CHANGED, oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@fbdc7c, newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@fbdc7c ] 09.07.2013 06:49:26.719 *INFO* [main] org.apache.sling.event.impl.jobs.queues.ParallelJobQueue.test Outdating queue test, renaming to testoutdated(4379095). 09.07.2013 06:49:26.719 *INFO* [main] org.apache.sling.event.impl.jobs.TopologyCapabilities Detected capabilities of 27cdd24a-1f80-4f79-a115-001521e8d6d6 : / 09.07.2013 06:49:26.720 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [112] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.721 *INFO* [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.sling.event.jobs.QueueConfiguration.13628013-f4b2-403f-969a-8dc98e216560)] org.apache.sling.event Service [org.apache.sling.event.jobs.QueueConfiguration.13628013-f4b2-403f-969a-8dc98e216560,111] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.723 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent STOPPING 09.07.2013 06:49:26.723 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [82] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.724 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [83] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.724 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [84] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.725 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [85] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.725 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [86] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.725 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [87] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.726 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [88] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.726 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [89] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.726 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [90] ServiceEvent UNREGISTERING 09.07.2013 06:49:26.727 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent STOPPED 09.07.2013 06:49:26.727 *INFO* [main] org.ops4j.pax.exam.raw.extender.intern.TestBundleObserver Unregistered testcase [org.ops4j.pax.exam.raw.extender.intern.Probe@de808a.] 09.07.2013 06:49:26.727 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent UNRESOLVED 09.07.2013 06:49:26.729 *INFO* [main] PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent UNINSTALLED 09.07.2013 06:49:26.730 *INFO* [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING 09.07.2013 06:49:26.730 *INFO* [FelixDispatchQueue] org.apache.felix.framework FrameworkEvent PACKAGES REFRESHED 09.07.2013 06:49:26.730 *INFO* [FelixStartLevel]
Re: Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1723
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
