All succeed now! Thanks,-Challen
-----Original Message----- From: Bolz, Michael [mailto:[email protected]] Sent: 2014年7月31日 19:59 To: [email protected] Subject: Re: [OLINGO-377] Current state Hi together, With the last commit (id: 29d374740ff9c7d97a1ce90d3508305545def899) the issue is fixed. Can you please verify that the fix also works in your environment. Kind regards, Michael On 31.07.14 12:52, "Amend, Christian" <[email protected]> wrote: >Hi Challen, > >Michael and I are on it to fix this. In the meantime you can use >-Dmaven.test.skip=true to skip the tests since our Jenkins works fine. > >Best Regards, >Christian > >-----Original Message----- >From: Challen He [mailto:[email protected]] >Sent: Donnerstag, 31. Juli 2014 11:27 >To: [email protected] >Subject: RE: [OLINGO-377] Current state > >Hi Michael, > >I find that the build on windows shows quite a few this kind of errors. >(also heard that on non-windows, the build is good.) > >Running org.apache.olingo.fit.v4.SingletonTestITCase >Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec <<< >FAILURE! - in org.apache.olingo.fit.v4.SingletonTestITCase >org.apache.olingo.fit.v4.SingletonTestITCase Time elapsed: 0 sec <<< >ERROR! >java.lang.IllegalArgumentException: addChild: Child name >'org.apache.olingo.server.tecsvc.TechnicalServlet' is not unique > at >org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java >:887) > at >org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at >org.apache.catalina.core.StandardContext.addChild(StandardContext.java:293 >1) > at org.apache.catalina.startup.Tomcat.addServlet(Tomcat.java:315) > at >org.apache.olingo.fit.server.TomcatTestServer$TestServerBuilder.addServlet >(TomcatTestServer.java:263) > at >org.apache.olingo.fit.AbstractBaseTestITCase.init(AbstractBaseTestITCase.j >ava:58) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm >pl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at >org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMetho >d.java:47) > at >org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable >.java:12) > at >org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod. >java:44) > at >org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java: >24) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at >org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.jav >a:264) > at >org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provi >der.java:153) > at >org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java >:124) > at >org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoa >der(ForkedBooter.java:200) > at >org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBoo >ter.java:153) > at >org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > > > >Thanks,-Challen > >From: Bolz, Michael [mailto:[email protected]] >Sent: 2014年7月28日 20:59 >To: [email protected] >Subject: [OLINGO-377] Current state > >Hello together, > >I changed the tests in the FIT module to use an embedded Tomcat (see: >'org.apache.olingo.fit.server.TomcatTestServer') instead of the Tomcat >provided via the 'cargo-plugin' (see [1]). >With this change (and some configuration) now the Cobertura Test Coverage >is available (see e.g.: >"https://builds.apache.org/job/olingo-377-cobertura/15/cobertura/"). > >Now I check compatibility with the current master branch (merge master on >the 'OLINGO-377-FIT' branch [2]). >If all is ok their are no objections I would afterwards (tomorrow) merge >the changes in the master. > >Kind regards, >Michael > >[1]: >https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=aaa >4f18e351777cae0a9c021dba1bededcfd63f0 >[2]: >https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=r >efs/heads/OLINGO-377-FIT
