You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2012/06/06 18:16:24 UTC

Jenkins build became unstable: stanbol-trunk-1.6 #934

See <https://builds.apache.org/job/stanbol-trunk-1.6/934/changes>


Re: Jenkins build became unstable: stanbol-trunk-1.6 #934

Posted by Fabian Christ <ch...@googlemail.com>.
2012/6/7 Rupert Westenthaler <ru...@gmail.com>:
> I will reopen STANBOL-654 and try to provide a fix later today. As
> this will need to go into the 0.10.0-incubating release of the
> Entityhub we will need to make an other RC. Sorry for that.

No problem. That's why we have (y)our tests ;) I can easily create a
new release package just for the Entityhub and call a new vote.

Best,
 - Fabian

Re: Jenkins build became unstable: stanbol-trunk-1.6 #934

Posted by Rupert Westenthaler <ru...@gmail.com>.
You are right!

The fix creates the query

    (((@de/rdfs\:label/:"frankf*") AND (@de/rdfs\:label/:"am Main")))

but this does not work. However

    (((@de/rdfs\:label/:frankf*) AND (@de/rdfs\:label/:"am Main")))

works. So it looks like that tokens with wildcard chars MUST NOT be in quotes.

THe reason why I have not noticed this was because the BundleList of
the Entityhub still referenced the 0.10.0 version and I implemented
the fix for "STANBOL-654" in 0.10.1 so the fix was not used in the
integration tests until you updated also the bundle list accordingly.

I will reopen STANBOL-654 and try to provide a fix later today. As
this will need to go into the 0.10.0-incubating release of the
Entityhub we will need to make an other RC. Sorry for that.

:(
Rupert

On Thu, Jun 7, 2012 at 12:26 AM, Fabian Christ
<ch...@googlemail.com> wrote:
> @Rupert, maybe you can say something about the failing tests.
>
> https://builds.apache.org/view/S-Z/view/Stanbol/job/stanbol-trunk-1.6/org.apache.stanbol$org.apache.stanbol.integration-tests/934/testReport/org.apache.stanbol.entityhub.it/
>
> It looks like they could be related to the fixed bug with the added
> '"' in STANBOL-654. It could be the case that the problem now occurs
> after the deps were fixed. It seems not to be a problem with wrong
> deps.
>
> Best,
>  - Fabian
>
> 2012/6/6 Apache Jenkins Server <je...@builds.apache.org>:
>> See <https://builds.apache.org/job/stanbol-trunk-1.6/934/changes>
>>
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt



-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: Jenkins build became unstable: stanbol-trunk-1.6 #934

Posted by Fabian Christ <ch...@googlemail.com>.
@Rupert, maybe you can say something about the failing tests.

https://builds.apache.org/view/S-Z/view/Stanbol/job/stanbol-trunk-1.6/org.apache.stanbol$org.apache.stanbol.integration-tests/934/testReport/org.apache.stanbol.entityhub.it/

It looks like they could be related to the fixed bug with the added
'"' in STANBOL-654. It could be the case that the problem now occurs
after the deps were fixed. It seems not to be a problem with wrong
deps.

Best,
 - Fabian

2012/6/6 Apache Jenkins Server <je...@builds.apache.org>:
> See <https://builds.apache.org/job/stanbol-trunk-1.6/934/changes>
>



-- 
Fabian
http://twitter.com/fctwitt

Jenkins build is back to stable : stanbol-trunk-1.6 #935

Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/stanbol-trunk-1.6/935/changes>