[
https://issues.apache.org/jira/browse/SOLR-13988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-13988.
-----------------------------------
Resolution: Fixed
I haven't seen this happen in a while. I'm still monitoring it, but will close
it for now.
> Harden CreateCollectionCleanupTest
> ----------------------------------
>
> Key: SOLR-13988
> URL: https://issues.apache.org/jira/browse/SOLR-13988
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Fix For: 8.4
>
> Attachments: SOLR-13988.patch
>
>
> This test counts on being unable to create
> {code}
> /some_invalid_dir/foo
> {code}
> And if it does somehow succeed, it'll affect the filesystem (which it
> apparently can at least on Windows under some circumstances and maybe Unix if
> you're super-user).
> It seems safer to create a temp dir and explicitly disable write permissions
> on it and use that instead. See attached patch. While I don't have a Windows
> machine to test on, the javadocs assure me that I can disable write perms
> this way on Windows...
> [~anshum][~tflobbe] Does this seem OK to you?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
