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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev