Seam tests fail from time to time. See https://jira.jboss.org/jira/browse/JBIDE-4496 and https://jira.jboss.org/jira/browse/JBIDE-3725

If they can't pass consistently every time, then they need to be:

Why is it dumb? If a test doesn't consistently pass, it shows there's a problem but doesn't quantify it or get you closer to fixing it. It's kind of like playing 20 Questions with someone who in addition to answering "Yes" or "No" will often answer "Maybe". My point is that if the question yields a Maybe reply (intermittent failures) then you need to ask a different question so you can always get a Yes (pass) or a No (fail). On 06/26/2009 04:34 PM, Rob Stryker wrote: > Not to pick on you nick, but that has to be one of the dumbest things > I've heard, as a test that can't pass every time could obviously just > show a bug that doesn't occur every time. > > Nick Boldt wrote: >> If they can't pass consistently every time, then they need to be: >> >

Hi, I was hoping it was not necessary for me to continue doing this but there is now tests that have been in the build for the last 13 failures and noone reacted to them, so here it goes: https://hudson.jboss.org/hudson/job/jbosstools-nightly-3.1.0.M2/293/testR... Latest 13(!) builds: AS: 1 JSFVerification: 1 I don't remember seeing any posts or jira on these 2. Rob Stryker got some insights ? Do they fail on your local build ? Alexey/Victor/Slava: What is the jsf verifier about ? Other minor ones: Lastest 2 builds: JMX: 1 New but reoccurring(?) failures: Seam: 3 failures JBossWS: 2 -max _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev