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 generate a new temporary directory that’s unique. I think ANT can do this for us (I think there is an ANT task to get a temporary name, which is assigned to a property). Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen https://www.thetaphi.de eMail: u...@thetaphi.de From: Robert Muir <rcm...@gmail.com> Sent: Sunday, January 19, 2020 11:47 PM To: dev@lucene.apache.org Subject: Re: New Policeman Jenkins Hardware: AMD Ryzen 7 3700X Octa-Core, DDR4 ECC, 2x1 Terabyte NVME SSD as RAID 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 these test indexes are "temp data"? so if the build respects java.io.tmpdir here, then imo it behaves nicely and gives user the chance to prevent hardware destruction. On Sun, Jan 19, 2020, 3:36 PM Dawid Weiss <dawid.we...@gmail.com <mailto:dawid.we...@gmail.com> > wrote: 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 doing then it should also make tests faster. Dawid
