This looks like a Hudson hiccup. Tyler is seeing excessive logging: Running org.apache.tika.cli.TikaCLIBatchIntegrationTest INFO - about to start driver INFO - about to start driver
Anyone else having problems building from a fresh trunk? -----Original Message----- From: Hudson (JIRA) [mailto:[email protected]] Sent: Wednesday, April 01, 2015 5:36 PM To: [email protected] Subject: [jira] [Commented] (TIKA-1330) Add robust tika-batch code [ https://issues.apache.org/jira/browse/TIKA-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391512#comment-14391512 ] Hudson commented on TIKA-1330: ------------------------------ ABORTED: Integrated in tika-trunk-jdk1.7 #596 (See [https://builds.apache.org/job/tika-trunk-jdk1.7/596/]) TIKA-1330 flush stacktrace writers (tallison: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1670756) * /tika/trunk/tika-batch/src/main/java/org/apache/tika/batch/FileResourceConsumer.java * /tika/trunk/tika-batch/src/main/java/org/apache/tika/util/TikaExceptionFilter.java TIKA-1330 clean up logging in tika-batch ant tika-app integration of tika-batch, take 2 (tallison: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1670751) * /tika/trunk/tika-batch/src/main/java/org/apache/tika/batch/FileResourceConsumer.java > Add robust tika-batch code > -------------------------- > > Key: TIKA-1330 > URL: https://issues.apache.org/jira/browse/TIKA-1330 > Project: Tika > Issue Type: Sub-task > Components: cli, general, server > Reporter: Tim Allison > Assignee: Tim Allison > Attachments: TIKA-1330v1-patch.zip > > > In my current design plan, I see creating a separate component "tika-batch" > that includes a small bit of configurable code to run Tika against a large > batch of documents. This code should be robust against OOM and hangs, and it > should have fairly robust logging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
