<div dir="ltr"><div><div>I've created a build in CI for the stress tests:<br><br><a href="http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_StressHotspotJdk6">http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_StressHotspotJdk6</a><br>
<br></div>Cheers<br></div>Dan<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Oct 6, 2013 at 12:07 AM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
the following change introduced a critical issue in the Lucene Directory:<br>
<br>
final Set<String> filesList = fileOps.getFileList();<br>
- String[] array = filesList.toArray(new String[0]);<br>
- return array;<br>
+ return filesList.toArray(new String[filesList.size()]);<br>
<br>
I'll leave it as a puzzler to figure why the change is able to cause trouble ;-)<br>
<br>
This generates a NPE in just a single second of running one of the<br>
stress tests or performance tests, but I'm guilty of not being able to<br>
make a normal unit test for this case.<br>
<br>
That module contains such limited code, that in the very rare<br>
occasions in which I apply some changes I re-run the included<br>
benchmarks; I realize I can't expect that from all of you, so..<br>
<br>
Should we enable some stress tests on CI?<br>
<br>
As a side warning consequence of this, the Lucene Directory in release<br>
6.0.0.CR1 is very unreliable [ISPN-3592].<br>
<br>
--Sanne<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</blockquote></div><br></div>