On Tuesday 21 October 2014 12:46:42 Sanne Grinovero wrote:
> I'm sceptical though on embarking into a PR process which assumes that
> we're going to be able to keep the testsuite green just because we
> decide so; let's first work on a green testsuite, and then proof that
> we can keep it that way for a resonsable time..

+1, green testsuite is a mandatory condition for any other action.
Let's start with smaller steps - I'd propose to make green Master JDK 7 first.

Currently [1] there fails these tests:
* ExampleConfigsIT.testXsiteConfig       - should be fixed by PR #2973

* HotRodRemoteCacheIT.testPutAsync - I investigated it few days ago, it's IMHO a not a random failure but a regular bug - ISPN-4813

* HotRodRemoteCacheIT.testCustom*, testEven* - I'll volunteer on investigating this issue
*  StateTransferSuppressIT.testRebalanceWith* - any volunteer for investigating this one?

Once the root causes are investigated, we can fix the issues and try to keep this build green.

> then we can talk about
> building something on reliable foundations.

actually, if there's a failing test and it's clear which commit has caused it, we can stop merging PRs from the developer
who has introduced the regression until he fix it. This should be clear message, that the first thing he should
work on is to fix the test. IMHO we can start with it now and don't need green testsuite for it

[1] http://ci.infinispan.org/viewLog.html?buildId=13323&tab=buildResultsDiv&buildTypeId=bt8&logTab=

_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev