ExecuteJavaTest testNoTimeOutForked fails

[Kev Jackson <fo...@gmail.com>]

Hi,

Just running the full test suite right now and I'm getting a failure  
on testNoTimeOutForked, and I cannot see why as it's a very very  
basic test!

Anyone experienced a similar failure?

Perhaps it's environmental, I'll look into that now

Kev
--
"All governments are in equal measure good and evil.  The best ideal  
is anarchy." - Leo Tolstoy


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org

Re: ExecuteJavaTest testNoTimeOutForked fails

[Kev Jackson <fo...@gmail.com>]

On 21 Jun 2006, at 16:16, Steve Loughran wrote:

> Antoine Levy-Lambert wrote:
>> I have occasional failures of one of these tests when my computer is
>> very loaded. Maybe we have some tests which work - say - when some  
>> CPU
>> is available,
>> but not when the CPU is at 100%.
>> Other than that. Can it be OS specific ? JDK specific ? Do not know.
>
> #of CPUs?
>
> Clock stuff is always a bit brittle; even if you say Sleep(1000)  
> the OS may only sleep you for 800ms, or whatever the clock  
> granularity is.

1 cpu (G4 1ghz)

If it's a brittle test I'm not going to worry about it, it's passing  
on gump fine, so I'm assuming local environment problem (ie too much  
load on my laptop).  All the others pass (after I changed the concat  
filter test to use the system line sep anyway).

I'd like to run through a pre-pre-release of ant 1.7 (trunk) to see  
if I'm capable of completing every stage *before* signing up to be  
the 'official' release manager - hence why I'm testing builds,  
getting pgp keys etc

Thanks
Kev

--
"Government is begotten of aggression, by aggression" - Herbert Spencer


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org

Re: ExecuteJavaTest testNoTimeOutForked fails

[Steve Loughran <st...@apache.org>]

Antoine Levy-Lambert wrote:
> I have occasional failures of one of these tests when my computer is
> very loaded. Maybe we have some tests which work - say - when some CPU
> is available,
> but not when the CPU is at 100%.
> 
> Other than that. Can it be OS specific ? JDK specific ? Do not know.

#of CPUs?

Clock stuff is always a bit brittle; even if you say Sleep(1000) the OS 
may only sleep you for 800ms, or whatever the clock granularity is.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org

Re: ExecuteJavaTest testNoTimeOutForked fails

[Antoine Levy-Lambert <an...@gmx.de>]

I have occasional failures of one of these tests when my computer is
very loaded. Maybe we have some tests which work - say - when some CPU
is available,
but not when the CPU is at 100%.

Other than that. Can it be OS specific ? JDK specific ? Do not know.

Regards,

Antoine

Kev Jackson wrote:
> Hi,
>
> Just running the full test suite right now and I'm getting a failure
> on testNoTimeOutForked, and I cannot see why as it's a very very basic
> test!
>
> Anyone experienced a similar failure?
>
> Perhaps it's environmental, I'll look into that now
>
> Kev
> -- 
> "All governments are in equal measure good and evil.  The best ideal
> is anarchy." - Leo Tolstoy
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org