Hi Robert,
+1
One small thing: It should use java.io.tmpdir, but append its own process id or
something like that to it, so multiple runs (like on Jeekins) in parallel do
not override each other. Maybe just use tmpname (the corresponding
java.nio.file.Files function) or similar to
agreed. for all situations it may not help. but for my test 0 bytes were
left at the end. i watched the io and usage as tests ran and the usage only
even peaks at megabytes.
just death by a thousand stabs... literally. gazillions of tests writing
only a few MB each.
i think we can all agree
...and safe your SSD from death.
Some statistics: in 12 hours the macOS slave wrote 114 Gigabytes to it's
virtual harddisk - according to Darwin's top implementation, which displays
disk IO since bootup of kernel.
Uwe
Am January 19, 2020 8:35:55 PM UTC schrieb Dawid Weiss :
>> Maybe we should
> Maybe we should open an issue. For example it would be good to fix the
> gradle build here too.
>
It's definitely possible to relocate those folders (gradle-wise). I don't
think it buys anything for Windows users or for those who have /tmp mounted
on a physical drive but if you know what you're
On Thu, Jan 16, 2020 at 2:38 AM Uwe Schindler wrote:
> So Lucene and Solr tests are eating your SSD, be aware of that!!!
>
>
By default all the tests are writing indexes to build/ directory where your
source checkout is, I think this is a bad default?
As a workaround I can manually pass
