Sorry, I thought I'd read that it had some sort of mop-up capability.
On Thu, Feb 17, 2011 at 4:24 AM, Jörn Kottmann wrote:
> On 2/16/11 12:55 PM, Benson Margulies wrote:
>>
>> Have you tried failsafe instead of surefire? This sounds more like an
>> integration test.
>
> Thanks for that advice. N
On 2/16/11 12:55 PM, Benson Margulies wrote:
Have you tried failsafe instead of surefire? This sounds more like an
integration test.
Thanks for that advice. Now I switched to failsafe, but the error remains
the same. If the maven process is terminated via the abort button the
test process stays
On Wed, Feb 16, 2011 at 10:26 AM, Jörn Kottmann wrote:
> First I kindly ask to get this still running process killed on hudson
> (solaris2).
> I do not have shell access to that machine.
Done (we do this as a routine as many builds leave processes)
/niklas
Have you tried failsafe instead of surefire? This sounds more like an
integration test.
On Wed, Feb 16, 2011 at 4:26 AM, Jörn Kottmann wrote:
> Hi all,
>
> I am from the UIMA team and we set up hudson to test UIMA-AS (also job
> name).
> Maven forks a process to run the tests in. It seems that th
Hi all,
I am from the UIMA team and we set up hudson to test UIMA-AS (also job
name).
Maven forks a process to run the tests in. It seems that this process is
not
stopped when our tests hangs and the build is aborted either manually
or via the configured time out.
First I kindly ask to get th
