[ 
https://issues.apache.org/jira/browse/SOLR-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995387#comment-12995387
 ] 

Gunnlaugur Thor Briem edited comment on SOLR-2367 at 2/16/11 5:09 PM:
----------------------------------------------------------------------

Patch to address this issue. Creates conf directories under work directory 
before test runs, and suppresses a warning.

The console noise that remains is some XML parsing failure, which may or may 
not be meaningful (I don't know) — at least now it is visible. :)

This patch is against branch_3x as of just now.

      was (Author: gthb):
    Patch to address this issue. Creates conf directories under work directory 
before test runs, and suppresses a warning.

The console noise that remains is some XML parsing failure, which may or may 
not be meaningful (I don't know) — at least now it is visible. :)
  
> DataImportHandler unit tests are very noisy
> -------------------------------------------
>
>                 Key: SOLR-2367
>                 URL: https://issues.apache.org/jira/browse/SOLR-2367
>             Project: Solr
>          Issue Type: Improvement
>          Components: Build, contrib - DataImportHandler
>            Reporter: Gunnlaugur Thor Briem
>            Priority: Trivial
>         Attachments: SOLR-2367.patch
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> Running DataImportHandler unit tests emits a lot of console noise, mainly 
> stacktraces because dataimport.properties can't be written. This makes it 
> hard to scan the output for useful information.
> I'm attaching a patch to get rid of most of the noise by creating the conf 
> directory before test runs so that the properties file write doesn't fail.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to