[infinispan-dev] infinispan test suite, reloaded

Mircea Markus mmarkus at redhat.com
Thu Jul 10 10:13:09 EDT 2014


On Jul 10, 2014, at 15:03, Sanne Grinovero <sanne at infinispan.org> wrote:

> The important point for me is that patches don't get merged if they
> introduce any regression. I hope that rule stays?
> BTW this matches with the "classic" approach as far as I know it.

yes. A patch might pass the test when integrated and cause intermittent failures later on, so it's not straight forward to avoid patches introducing regressions, nor to identify which patch has caused it so that we can roll it back. 

> 
> On 10 July 2014 14:04, Mircea Markus <mmarkus at redhat.com> wrote:
>> I just had a chat with Dan and we don't think the current process for the test suite works. Not hard to see why, the suite is almost never green. So we will adopt a more classic and simple approach: if a test fails a blocker JIRA is created for it and assigned to a component lead then team member who'll start working on it *immediately*. Dan will be watch dog starting today so please expect blocker JIRAs coming your way and treat them accordingly.
>> 
>> Cheers,
>> --
>> Mircea Markus
>> Infinispan lead (www.infinispan.org)
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> _______________________________________________
> 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)







More information about the infinispan-dev mailing list