We don't have a configured maximum duration for the stress tests. The
stress build take about 13 minutes now, but enabling all the stress tests
will probably increase the duration.
I didn't want to delay regular builds, I've scheduled it to run every night
at 03:00 GMT instead of running after
That works as long as someone runs the stress tests before tagging a release.
Sanne
On 9 October 2013 14:19, Dan Berindei dan.berin...@gmail.com wrote:
We don't have a configured maximum duration for the stress tests. The stress
build take about 13 minutes now, but enabling all the stress
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.berin...@gmail.com wrote:
I've created a build in CI for the stress tests:
Hi all,
the following change introduced a critical issue in the Lucene Directory:
final SetString filesList = fileOps.getFileList();
- String[] array = filesList.toArray(new String[0]);
- return array;
+ return filesList.toArray(new String[filesList.size()]);
I'll leave it
