[infinispan-dev] Random test failures should be fixed before 5.2.0.FINAL

[Mircea Markus]

+1 for stabilising the test suite.
Note that ATM there are critical/blocker in the JIRA that should be tackled first as are either required by QA or users. Post CR1 we should all focus on the test suite stability.

On 18 Dec 2012, at 12:45, Galder Zamarreño wrote:

> Hi,
> 
> We have a load of random tests failing which have been identified:
> https://issues.jboss.org/issues/?filter=12317273
> 
> Everyone should look at their own assigments and aim to fix them for 5.2.
> 
> I see no reason to carry on with random tests failing further on (i.e. 5.3 or 6…). A lot of those tests have TRACE logs btw…
> 
> For example: https://issues.jboss.org/browse/ISPN-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel - @Mircea, a trace log is available for a random failure, why move it to 6.0?
moved back to 5.2.
> 
> Cheers,
> --
> Galder Zamarreño
> galder at redhat.com
> twitter.com/galderz
> 
> Project Lead, Escalante
> http://escalante.io
> 
> Engineer, Infinispan
> http://infinispan.org
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

Cheers,
-- 
Mircea Markus
Infinispan lead (www.infinispan.org)




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20121218/35707d0a/attachment-0001.html