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

Hudson commented on NUTCH-2771:
-------------------------------

SUCCESS: Integrated in Jenkins build Nutch ยป Nutch-trunk #174 (See 
[https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/174/])
NUTCH-2771 Tests in nightly builds: skip long runners (snagel: 
[https://github.com/apache/nutch/commit/e1b8dbe909b0f8c181dcb5ee0e7e072f27f82cbb])
* (edit) src/test/org/apache/nutch/segment/TestSegmentMergerCrawlDatums.java
* (edit) src/test/org/apache/nutch/segment/TestSegmentMerger.java
* (edit) build.xml


> Tests in nightly builds: speed up long runners
> ----------------------------------------------
>
>                 Key: NUTCH-2771
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2771
>             Project: Nutch
>          Issue Type: Improvement
>          Components: build, test
>    Affects Versions: 1.16
>            Reporter: Sebastian Nagel
>            Assignee: Sebastian Nagel
>            Priority: Minor
>             Fix For: 1.21
>
>
> The Nutch tests run by "ant test" or "ant nightly") take rather long to run. 
> Although all tests are implemented as JUnit tests, some tests are more 
> integration tests, eg. launching a Jetty web server and fetching documents 
> from it. It's nice to have also higher level tests, and they are expected to 
> long runner than a simple unit test. However, some of the test classes take 
> really long to run (times taken from 
> https://builds.apache.org/job/Nutch-trunk/3663/consoleText):
> {noformat}
>     [junit] Running org.apache.nutch.segment.TestSegmentMergerCrawlDatums
>     [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 133.898 sec
>     [junit] Running org.apache.nutch.segment.TestSegmentMerger
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 101.026 sec
>     [junit] Running org.apache.nutch.crawl.TestGenerator
>     [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 46.03 sec
>     [junit] Running org.apache.nutch.fetcher.TestFetcher
>     [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 17.805 sec
>     [junit] Running org.apache.nutch.urlfilter.fast.TestFastURLFilter
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 12.36 sec
>     [junit] Running org.apache.nutch.parse.tika.TestPdfParser
>     [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 11.974 sec
>     [junit] Running org.apache.nutch.parse.tika.TestImageMetadata
>     [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 9.113 sec
>     [junit] Running org.apache.nutch.parse.feed.TestFeedParser
>     [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 6.369 sec
>     [junit] Running org.apache.nutch.crawl.TestInjector
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 6.15 sec
> {noformat}
> We could try to speed up at least some of these long-running tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to