Hi all,
Just to followup:

with a clean, empty repository:

`$ mvn -Dmaven.repo.local=/tmp/any23-repo clean install`

I can successfully compile the code but there are still tests
failures, see below...

Maybe we should increase the timeout response?
TIA,
-Simo

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Tests in error:
  testDemoCodeSnippet2(org.apache.any23.Any23Test): Read timed out

Tests run: 465, Failures: 0, Errors: 1, Skipped: 1

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Any23 ...................................... SUCCESS [20.952s]
[INFO] Apache Any23 :: Core .............................. FAILURE [1:53.306s]
[INFO] Apache Any23 :: Plugins :: Basic Crawler .......... SKIPPED
[INFO] Apache Any23 :: Plugins :: HTML Scraper ........... SKIPPED
[INFO] Apache Any23 :: Plugins :: Office Scraper ......... SKIPPED
[INFO] Apache Any23 :: Plugins :: Integration Test ....... SKIPPED
[INFO] Apache Any23 :: Service ........................... SKIPPED
[INFO] Apache Any23 :: Sources distribution module ....... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:17.326s
[INFO] Finished at: Thu Jun 28 10:57:12 CEST 2012
[INFO] Final Memory: 22M/2039M
[INFO] ------------------------------------------------------------------------


http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Thu, Jun 28, 2012 at 10:46 AM, Michele Mostarda
<[email protected]> wrote:
> This is another stuff. Any23 relies on some online resources to perform
> more sophisticated tests.
> In this case the CrawlerTest is trying to crawl 10 pages from a site
> containing RDF content and
> in the end assert that the quantity of extracted triples is compliant to an
> expected one.
>
> If the target site is congested the test could fail. Nothing strange.
> I will double check that anything changed in the target site.
>
> Mic
>
> On 27 June 2012 22:13, Lewis John Mcgibbney <[email protected]>wrote:
>
>> OK so when I completely delete everything in my entire ~/m2 cache and
>> run mvn clean package I get
>>
>> ------------------------------------------------------------------------
>> Apache Any23 :: crawler
>> ------------------------------------------------------------------------
>>
>> Deleting content of:
>> /tmp/crawler-metadata-c2788d22-6db7-4312-b9d8-f54849057c41/frontier
>>  INFO [pool-1-thread-1] Crawler 1 started.
>>  INFO [pool-1-thread-1] Crawler 2 started.
>>  INFO [pool-1-thread-1] Crawler 3 started.
>>  INFO [pool-1-thread-1] Crawler 4 started.
>>  INFO [pool-1-thread-1] Crawler 5 started.
>>  INFO [pool-1-thread-1] Crawler 6 started.
>>  INFO [pool-1-thread-1] Crawler 7 started.
>>  INFO [pool-1-thread-1] Crawler 8 started.
>>  INFO [pool-1-thread-1] Crawler 9 started.
>>  INFO [pool-1-thread-1] Crawler 10 started.
>> Processing page: [http://eventiesagre.it/]
>> Processing page:
>> [
>> http://eventiesagre.it/Eventi_Feste/21039505_Le+Giornate+Di+San+Paolino.html
>> ]
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.589
>> sec <<< FAILURE!
>> Total Documents: 0, Total Triples: 0
>>
>> The package target fails here, the stack trace from the failed test is
>> as follows
>>
>>
>> -------------------------------------------------------------------------------
>> Test set: org.apache.any23.cli.CrawlerTest
>>
>> -------------------------------------------------------------------------------
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.59
>> sec <<< FAILURE!
>> testCLI(org.apache.any23.cli.CrawlerTest)  Time elapsed: 10.266 sec
>> <<< FAILURE!
>> java.lang.AssertionError
>>        at org.junit.Assert.fail(Assert.java:92)
>>        at org.junit.Assert.assertTrue(Assert.java:43)
>>        at org.junit.Assert.assertTrue(Assert.java:54)
>>        at org.apache.any23.cli.CrawlerTest.testCLI(CrawlerTest.java:93)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>        at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>        at java.lang.reflect.Method.invoke(Method.java:597)
>>        at
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>>        at
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>>        at
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>>        at
>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>>        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>>        at
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>>        at
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>>        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>>        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
>>        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
>>        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
>>        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
>>        at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>>        at
>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
>>        at
>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
>>        at
>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> On Wed, Jun 27, 2012 at 9:45 AM, Michele Mostarda
>> <[email protected]> wrote:
>>
>> I'm pretty much stumped on this one...
>>
>> Lewis
>>
>
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: [email protected]
> site : http://www.michelemostarda.com

Reply via email to