Hey,
almost done with the rewrite of the locking mechanisms..
the bug removed is the busywait bug of the previous "leaky-lock" but in all
instance what we are looking for is hangs in *particular threads*. I really
don't know how we can automate that.
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Saturday, June 30, 2001 9:59 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] jbosstest automated testing: Test hangs not
|detected.
|
|
|This really seems to be a bug in the junit task as it supports a
|timeout option
|which we are using, but when the timeout occurs a blank file is output
|rather than a file containing an error. We use our own custom Ant task to
|concatenate the various results into the overall report so I'll look into
|updating that to detect this condition.
|
|----- Original Message -----
|From: "Ole Husgaard" <[EMAIL PROTECTED]>
|To: "Jboss-Development" <[EMAIL PROTECTED]>
|Sent: Saturday, June 30, 2001 3:48 PM
|Subject: [JBoss-dev] jbosstest automated testing: Test hangs not detected.
|
|
|> Hi,
|>
|> When running the automated jbosstest on an old slow
|> machine, the banktest sometimes times out.
|> This leaves an empty Test-org.jboss.test.bank.Main.xml
|> file.
|> When the *.xml files are concatenated, the empty file
|> goes unnoticed, and the final report does not include
|> the fact that the bank test timed out.
|>
|> I guess this implicates that hung or timed out tests
|> are NOT detected by the automated testing.
|>
|> Unfortunately I am not very familiar with Ant, and
|> cannot see how to detect an empty file from Ant.
|>
|> Any ideas anyone?
|>
|>
|> Best Regards,
|>
|> Ole Husgaard.
|>
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
