[
https://issues.apache.org/jira/browse/LUCENE-9158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020572#comment-17020572
]
Uwe Schindler commented on LUCENE-9158:
---------------------------------------
My other problem: everything is now in same directory, so events files and
crash dumps are no longer per module. Currently all those files are archived by
Jenkins.
With this patch it's no longer possible to use a per module workdir, as you
cannot pass this by command line.
IMHO, maybe keep the current default if the property "is.jenkins.run" is "true".
In general I am a fan of everything in the build folder by default (we agreed
on that when setting everything up).
It's very easy for people who want to protect their SSD by adding the workDir
property to their lucene.build.properties file.
-1 for a default outside checkout. I know I was complaining, but I changed my
mind.
> Fix tests to respect java.io.tmpdir by default
> ----------------------------------------------
>
> Key: LUCENE-9158
> URL: https://issues.apache.org/jira/browse/LUCENE-9158
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/test
> Reporter: Robert Muir
> Priority: Major
> Attachments: LUCENE-9158.patch
>
>
> Currently the tests destroy your SSDs by writing temp test data to
> {{build/test/}} in your checkout.
> It would be better to respect {{java.io.tmpdir}} for where all the temporary
> files get written. This way, if someone has configured their
> system/environment variables appropriately, it won't destroy SSD.
> On linux it may work by default in many cases, as a lot of linux systems
> mount {{/tmp}} on tmpfs by default.
> On windows users could have created a [RAM
> drive|https://en.wikipedia.org/wiki/List_of_RAM_drive_software] such as
> {{R:}} and have {{TMP}} environment variable pointed at it, we should respect
> that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
