Hi After looking at the timetable [1] of the last build I made some modifications [2] that should speedup the build process.
Hopefully this improves the situation best Rupert [1] https://builds.apache.org/job/stanbol-trunk-1.6/248/ [2] http://svn.apache.org/viewvc?rev=1140157&view=rev On Mon, Jun 27, 2011 at 3:11 PM, Olivier Grisel <[email protected]> wrote: > 2011/6/27 Fabian Christ <[email protected]>: >> Hi, >> >> yes I have the same problem as Olivier. >> >> Tests in error: >> testGetScopes(org.apache.stanbol.ontologymanager.web.JettyServerTest) >> testRemoval(org.apache.stanbol.ontologymanager.web.JettyServerTest) >> >> I did: >> >> rm ~/.m2/repository/org/apache/stanbol >> mvn clean install > > Indeed that fixes my issue, so it's probably not related to the > timeout issue Rupert is talking about. No I have extremly slow tests > such as: > > Running org.apache.stanbol.ontologymanager.ontonet.registry.TestRegistry > INFO [main] (ONManagerImpl.java:308) - id: ontonet > > Looks like it's downloading the Internet. > > We should not enable any test that depends on Internet resource in the > maven build. Otherwise the continuous integration tests (and thus > jenkins) will fail randomly based on Internet and remote resources > availability and stability. > > Having a jenkins build that fails randomly independently of the actual > state of the code base is a major technical debt we should get rid off > as soon as possible. > > IMHO those test should be deactivated in the short term, and rewritten > to use only local resources (smallish files distributed in the > src/test/resources folder of the corresponding modules) in the medium > term. > > -- > Olivier > http://twitter.com/ogrisel - http://github.com/ogrisel > -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
