The problem is that nothing is blowing up, the build just gets stuck and hangs until the build timeout plugin steps in and aborts the build
The hang is in the tests for the remote endpoint driver which are standing up Fuseki instances. However if there was some contention for ports in the tests I would expect the tests to just plain fail. I suspect there may be some deadlock of some sort happening when running the tests on the server but it's hard to tell where/what the deadlock is. I am turning the log level for the tests in question to DEBUG and will re-run a build to see if that yields anything more useful. Rob On 8/8/13 6:53 AM, "Andy Seaborne" <[email protected]> wrote: >On 01/08/13 20:56, Rob Vesse wrote: >> I've removed it from the main build for now. For some reason it is >> getting stuck (but not crashing) on the Apache build server. This is >> despite it building fine locally and on our internal build servers. >> >> Not sure how to proceed on this - is it worth setting up a separate >>build >> for JDBC on the Apache build servers to help try and isolate the >>problem? >> >> Rob > >What exactly is blowing up? > >The Apache build servers have all sorts of things on them and a wide >range of plugins, which itself can a problem. > > Andy > >> >> >> On 8/1/13 11:45 AM, "Rob Vesse" <[email protected]> wrote: >> >>> I've moved Jena JDBC from Experimental into Trunk and added it to the >>> main build. The builds are a little nosier that some of the other >>> modules so may want some tweaking to avoid spurious build output. >>> >>> I haven't attempted to figure out how to add it to the distro because I >>> know nothing about Maven Assembly plugin >>> >>> Rob >> >
