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

Sebastian Nagel commented on NUTCH-2771:
----------------------------------------

Moving to 1.18 for now. After a closer look: all these tests are useful. One 
option could be to mark long-runners using [JUnit 5 
tags|https://junit.org/junit5/docs/current/user-guide/#writing-tests-annotations]
 which would allow to run them separately.

> 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.17
>
>
> 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.3.4#803005)

Reply via email to