You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2012/06/19 03:41:56 UTC

Jenkins build became unstable: Derby-10.9-suites.All #15

See <https://builds.apache.org/job/Derby-10.9-suites.All/15/changes>

Jenkins build is back to stable : Derby-10.9-suites.All #16

Posted by Apache Jenkins Server <je...@builds.apache.org>.

See <https://builds.apache.org/job/Derby-10.9-suites.All/16/>

Re: Jenkins build became unstable: Derby-10.9-suites.All #15

Posted by Kristian Waagan <kr...@oracle.com>.

On 19.06.12 03:41, Apache Jenkins Server wrote:
> See<https://builds.apache.org/job/Derby-10.9-suites.All/15/changes>
>

Looks like four tests failed because of network issues. First:

Caused by: org.apache.derby.client.am.DisconnectException: Error for 
batch element #0: Error for batch element #0: Error for batch element 
#0: A communications error has been detected: Connection reset.

then followed by:

java.net.ConnectException : Error connecting to server localhost on port 
1527 with message Connection refused.

I've manually scheduled a new run.

-- 
Kristian