You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2013/07/05 14:50:02 UTC
TestService: different on windows.
On 05/07/13 12:55, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/Jena_Development_Test_Windows/changes>
>
Rob,
FYI: we're getting
java.lang.AssertionError:
Expected SocketException (or subclass thereof), instead got:
org.apache.http.conn.ConnectTimeoutException Connect to
example.com:40000 timed out
at org.junit.Assert.fail(Assert.java:88)
at
com.hp.hpl.jena.sparql.engine.http.TestService.testNumericTimeout(TestService.java:74)
It seem Windows has a different cause exception to Linux. I've
generalised the tests to accept both causes.
Andy
Re: TestService: different on windows.
Posted by Rob Vesse <rv...@yarcdata.com>.
That's odd, presumably this is down to the JDKs on the different platforms
using the low level system APIs slightly differently resulting in
exceptions bubbling up differently
Rob
On 7/5/13 5:50 AM, "Andy Seaborne" <an...@apache.org> wrote:
>On 05/07/13 12:55, Apache Jenkins Server wrote:
>> See
>><https://builds.apache.org/job/Jena_Development_Test_Windows/changes>
>>
>
>Rob,
>
>FYI: we're getting
>
>java.lang.AssertionError:
>Expected SocketException (or subclass thereof), instead got:
>org.apache.http.conn.ConnectTimeoutException Connect to
>example.com:40000 timed out
> at org.junit.Assert.fail(Assert.java:88)
> at
>com.hp.hpl.jena.sparql.engine.http.TestService.testNumericTimeout(TestServ
>ice.java:74)
>
>It seem Windows has a different cause exception to Linux. I've
>generalised the tests to accept both causes.
>
> Andy
>
>