Not a known problem, first time I've seen that test fail, but almost
certainly not related to the JDK change. It looks to be mainly a test
issue, the expected connection failure happened before it was
expecting..a bit of surprise that it is actually attempting the
underlying connection earlier than
I notice one failure since the change, but i am not convinced it is related:
Job: Qpid-JMS-Test-JDK8
Failing test:
org.apache.qpid.jms.provider.failover.FailoverProviderTest.testMaxReconnectAttempts
The change to the job was simple
from:
latest1.8
to:
JDK 1.8 (latest)
Is this already a known
Great, thanks Keith. I've yet to read all of those but figured there
would need to be some updates unless infra made them for everyone.
Robbie
On 3 August 2016 at 17:01, Keith W wrote:
> In response to infra@a.o's initiative to consolidate the JDK versions
> available on the Apache Jenkins CI sl
In response to infra@a.o's initiative to consolidate the JDK versions
available on the Apache Jenkins CI slaves, I have updated all Qpid
jobs that were using JDK labels that have been marked as deprecated to
the equivalents that are not.
https://cwiki.apache.org/confluence/display/INFRA/JDK+Instal
