[infinispan-dev] Timing related tests

[Mircea Markus]

This is a very tricky one indeed. These might fail as well e.g. if we increase the number of concurrent threads running the test suite. I remember when switching from 1 thread to 10 there were many of these failing.
I think your suggestion makes sense.

On 10 Jun 2011, at 13:02, Manik Surtani wrote:
> Some tests - like ExpiryTest - rely on certain timings for the test to run, and due to thread scheduling on our parallel test suite, tend to occasionally fail on certain environments such as CloudBees:
> 
> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.infinispan$infinispan-core/67/testReport/org.infinispan.expiry/ExpiryTest/org_infinispan_expiry_ExpiryTest_testLifespanExpiryInPutAll/
> 
> In this example, entries are placed in the data container with a 30 second lifespan, tested for existence, wait 30s, and test for non-existence.  The failure here is that the first test for existence fails since the thread is de-scheduled for a period of time between storing the entry and the first test.
> 
> Upping the lifespan just moves the problem - and makes the test suite run slower (got to wait for that lifespan before testing again).
> 
> How about we group such tests into a new group, "timeSensitiveTests", and *don't* run these on CI environments (but *do* run them on local environments where response times are more reasonable/predictable)?
> 
> Thoughts?
> 
> Cheers
> Manik
> --
> Manik Surtani
> manik at jboss.org
> twitter.com/maniksurtani
> 
> Lead, Infinispan
> http://www.infinispan.org
> 
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20110610/b3178e1e/attachment.html