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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
