Hi Rupert,

On 12 January 2013 22:48, Rupert Westenthaler
<[email protected]> wrote:
> Hi Enrico,
>
> I can confirm that the unit test hangs.
>
>> Now, if I remember correctly we decided that tests should not rely on
>> remote services, but since I have been not much active in the last
>> period I probably missed something.
>
> This is correct for the integration tests, but not necessarily the
> case for unit tests. Tests for Engines based on a remote service  -
> like Celi - need to connect the remote service for testing. Otherwise
> changes in the remote service that do break the Engines implementation
> would not be detectable.
I don't see the difference with IT, nevertheless I understand your
point that these tests are useful.

>
> However such tests do not fail if the remote Service is unreachable or
> reports a 5**. In case of the CELI engine we need to add an reasonable
> short (e.g. 10sec) timeout to avoid situations like the current one.
Yes, skipping the test with a warning message, I guess you mean.

For the moment I simply skipped it, to go with the build.

Thank you

Enrico

>
> best
> Rupert
>
> On Sat, Jan 12, 2013 at 11:32 PM, Enrico Daga <[email protected]> wrote:
>> Hi,
>>
>> I am trying to build Stanbol from a clean local repo, also to better
>> verify references to parent poms and related issues, but the process
>> goes on smmothly until this test, which hanged.
>>
>> I stopped the process and relaunched it with -rf
>> :org.apache.stanbol.enhancer.engines.celi and, after this output:
>>
>> 22:25:49,893 DEBUG [LanguageIdentifierClientHTTP] Request to
>> http://linguagrid.org/LSGrid/ws/language-identifier took 981ms
>> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.507 sec
>> Running 
>> org.apache.stanbol.enhancer.engines.celi.classification.impl.CeliClassificationEnhancementEngineTest
>> 22:25:50,021 WARN  [Utils] no CELI license key configured for this
>> Engine, a guest account will be used (max 100 requests per day). Go on
>> http://linguagrid.org for getting a proper license key.
>>
>> it hanged again.
>> I guess it is trying to connect to a remote service,
>>
>> It may be because of some firewalls in my actual  sub network (don't
>> know which port is invoked by the test, if it is an http port it
>> should pass without problems).
>>
>> Now, if I remember correctly we decided that tests should not rely on
>> remote services, but since I have been not much active in the last
>> period I probably missed something.
>>
>> Any hint?
>>
>> Enrico
>>
>> --
>> Enrico Daga
>>
>> --
>> http://www.enridaga.net
>> skype: enri-pan
>
>
>
> --
> | Rupert Westenthaler             [email protected]
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen



-- 
Enrico Daga

--
http://www.enridaga.net
skype: enri-pan

Reply via email to