On 1 May 2013 13:57, Lewis John Mcgibbney <[email protected]> wrote:
> Hi All, > > So now we have three problematic tests namely the following > > > - org.apache.any23.extractor.html.HListingExtractorTest.testKelkoo< > https://builds.apache.org/job/Any23-trunk/org.apache.any23$apache-any23-core/648/testReport/junit/org.apache.any23.extractor.html/HListingExtractorTest/testKelkoo/ > > > - org.apache.any23.extractor.html.HListingExtractorTest.testKelkooFull< > https://builds.apache.org/job/Any23-trunk/org.apache.any23$apache-any23-core/648/testReport/junit/org.apache.any23.extractor.html/HListingExtractorTest/testKelkooFull/ > > > - org.apache.any23.cli.CrawlerTest.testCLI< > https://builds.apache.org/job/Any23-trunk/org.apache.any23.plugins$apache-any23-basic-crawler/648/testReport/junit/org.apache.any23.cli/CrawlerTest/testCLI/ > > > > > Locally for me the latter fails as well on line 93 of the test which merely > assert whither extracted statements are greater than 0! > Again, this relies upon a dynamic site, which is bad practice IMHO. We > would be better setting up a local Jetty server pushing the static content > there and biting rhe bullet until someone steps up to address the tests > we've temporarily been setting to @Ignore. In short I propose to do the > same for this one. Any objections? > > The HListingExtractor tests both pass for me locally so i have no idea what > is wrong here. > Does the Jenkins server have access to the site? The HListingExtractor tests have intermittently failed for me in the past. I will commit the ANY23-156 patch now if you have not already done it. Peter
