lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5650) createTempDir and associated functions no longer create
Date Tue, 06 May 2014 21:40:17 GMT


Robert Muir commented on LUCENE-5650:

The main upside is it increases sandboxing: being lazy and letting tests read/write to CWD
means you have a higher possibility of failures because tests "interfere with each other".
When they make their own temp dirs this doesnt happen.

But, as soon as a logging framework gets in my way on something, i drop out. I just cant deal
with them :)

Maybe someone else can follow thru the final inch so we can ban this, or at least only allow
it for the modules that aren't fixed.

> createTempDir and associated functions no longer create
> ----------------------------------------------------------------------
>                 Key: LUCENE-5650
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Ryan Ernst
>            Assignee: Dawid Weiss
> The recent refactoring to all the create temp file/dir functions (which is great!) has
a minor regression from what existed before.  With the old {{LuceneTestCase.TEMP_DIR}}, the
directory was created if it did not exist.  So, if you set {{}} to {{"./temp"}},
then it would create that dir within the per jvm working dir.  However, {{getBaseTempDirForClass()}}
now does asserts that check the dir exists, is a dir, and is writeable.
> Lucene uses {{"."}} as {{}}.  Then in the test security manager, the per
jvm cwd has read/write/execute permissions.  However, this allows tests to write to their
cwd, which I'm trying to protect against (by setting cwd to read/execute in my test security

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message