Nice!
Is that going to work out with our hardware?
We'll need to be careful now with the configured duration of each such test.
On 7 October 2013 13:48, Dan Berindei <dan.berindei(a)gmail.com> wrote:
I've created a build in CI for the stress tests:
http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_StressHotsp...
Cheers
Dan
On Sun, Oct 6, 2013 at 12:07 AM, Sanne Grinovero <sanne(a)infinispan.org>
wrote:
>
> Hi all,
> the following change introduced a critical issue in the Lucene Directory:
>
> final Set<String> filesList = fileOps.getFileList();
> - String[] array = filesList.toArray(new String[0]);
> - return array;
> + return filesList.toArray(new String[filesList.size()]);
>
> I'll leave it as a puzzler to figure why the change is able to cause
> trouble ;-)
>
> This generates a NPE in just a single second of running one of the
> stress tests or performance tests, but I'm guilty of not being able to
> make a normal unit test for this case.
>
> That module contains such limited code, that in the very rare
> occasions in which I apply some changes I re-run the included
> benchmarks; I realize I can't expect that from all of you, so..
>
> Should we enable some stress tests on CI?
>
> As a side warning consequence of this, the Lucene Directory in release
> 6.0.0.CR1 is very unreliable [ISPN-3592].
>
> --Sanne
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev