The extended should finish in less than 55 minutes on a decent machine.The test runs its broker(s) on port 8118 and 8200. I doubt the ActiveMQ team runs on either of those port but who knows. Whenever you stop maven check if there is a java process still running. Not sure if I can do anything about it. If the launched process's output is not drained it will hang.
Jerry C On Fri, Feb 11, 2011 at 12:17 PM, Jörn Kottmann <[email protected]> wrote: > On 2/11/11 6:13 PM, Jaroslaw Cwiklik wrote: > >> It looks like there is another process running these tests. This only >> happens if you try start the test while another is still running. >> Maven launches a separate process to run tests. Perhaps you ve killed >> maven >> with CTRLC and the process running the test >> is hung since there is no other process draining its output. >> >> > I used the "abort" button in hudson to stop the hung build. It could > also conflict with a build done by the ActiveMQ team on the same machine. > I moved it now to solaris2, but we cannot use this machine for long running > (>1h) > build, I set the time limit to 55 minutes. Is that enough? > > On my macbook I got an error for three tests, I can do it again and > post them here. Or hopefully hudson will have the same tests failing. > > Jörn > >
