On 28 Feb 2011, at 17:24, Mircea Markus wrote:
On 28 Feb 2011, at 17:21, Manik Surtani wrote:
>
> On 22 Feb 2011, at 16:37, Jonathan Halliday wrote:
>
>>
>> That's actually going to change your test semantics slightly. You may
>> want to run in both optimized and non-optimized modes to ensure full
>> coverage - some code paths may not get exercised in one or the other case.
>
> Right; we actually DO want to test a full 2PC cycle. So we should disable any such
optimisations.
Both scenarios are equally important iMO, as I'd expect TM to use this optimisation.
Fair comment. Then we should set up Hudson to have 2 runs - one with and one without.
Hudson needs to be our definitive source of whether something is broken or not, and
running tests locally this behaviour can be controlled with a flag.
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Lead, Infinispan
http://www.infinispan.org