You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2014/04/05 10:55:14 UTC
[jira] [Updated] (LUCENE-5577) Temporary folder and file management
(and cleanup facilities)
[ https://issues.apache.org/jira/browse/LUCENE-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss updated LUCENE-5577:
--------------------------------
Description:
This is a spinoff of the work [~markrmiller@gmail.com], Uwe and me have initiated in SOLR-5914.
The core concept is this:
* every test should create its temporary folders and files in a sub-folder of one, easily identifiable, parent.
* the parent folder is named after the test class, with [org.apache.] removed for brevity. the folder name includes the master seed and a generated sequence integer, if needed, to easily demarcate different runs (and identify which run produced which files).
* temporary folder/ file creation routines should be available in LTC, so that no additional imports/ fiddling is needed.
* any temporary folders and files should be removable at the end of the suite (class), if all tests completes successfully. failure to do so (on windows) should be marked as an error
* there should be a way to temporarily mark a class to circumvent the above check (for known offenders)
* there should be a way for developers to leave temporary files on disk for further inspection (even in case of successful runs).
was:
This is a spinoff of the work [~markrmiller@gmail.com], Uwe and me have initiated in SOLR-5914.
The core concept is this:
* every test should create its temporary folders and files in a sub-folder of one, easily identifiable, parent.
* temporary folder/ file creation routines should be available in LTC, so that no additional imports/ fiddling is needed.
* any temporary folders and files should be removable at the end of the suite (class), if all tests completes successfully. failure to do so (on windows) should be marked as an error
* there should be a way to temporarily mark a class to circumvent the above check (for known offenders)
* there should be a way for developers to leave temporary files on disk for further inspection (even in case of successful runs).
> Temporary folder and file management (and cleanup facilities)
> -------------------------------------------------------------
>
> Key: LUCENE-5577
> URL: https://issues.apache.org/jira/browse/LUCENE-5577
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Minor
> Fix For: 4.8, 5.0
>
>
> This is a spinoff of the work [~markrmiller@gmail.com], Uwe and me have initiated in SOLR-5914.
> The core concept is this:
> * every test should create its temporary folders and files in a sub-folder of one, easily identifiable, parent.
> * the parent folder is named after the test class, with [org.apache.] removed for brevity. the folder name includes the master seed and a generated sequence integer, if needed, to easily demarcate different runs (and identify which run produced which files).
> * temporary folder/ file creation routines should be available in LTC, so that no additional imports/ fiddling is needed.
> * any temporary folders and files should be removable at the end of the suite (class), if all tests completes successfully. failure to do so (on windows) should be marked as an error
> * there should be a way to temporarily mark a class to circumvent the above check (for known offenders)
> * there should be a way for developers to leave temporary files on disk for further inspection (even in case of successful runs).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org