Hi Pascal & Cameleers, there is a matrix of installed JDK by node label[1], it could be a matter of just checking that the configured JDK is matched with the restriction label on the job configuration. And we should probably stick to "JDK 1.9 (latest)" as some versions get removed over time.
zoran [1] https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix On Thu, Nov 2, 2017 at 11:34 PM, Pascal Schumacher <pascalschumac...@gmx.net> wrote: > We should really get this fixed. :( > > Most of the time the java 9 job fails because the node building it does not > have java 9 installed. > > I created https://issues.apache.org/jira/browse/INFRA-15430 to ask if the is > a way to limit builds to nodes with java 9 installed. > > Also there are a few tests that seem to consistently fail on both java 8 and > 9: > > camel-cdi: > org.apache.camel.cdi.test.XmlErrorHandlerTest.org.apache.camel.cdi.test.XmlErrorHandlerTest > camel-cdi: > org.apache.camel.cdi.test.XmlRouteContextImportTest.org.apache.camel.cdi.test.XmlRouteContextImportTest > camel-mail: > org.apache.camel.component.mail.MailMimeDecodeHeadersTest.testNonAsciiMailSubject > camel-ribbon-starter: > org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest.testLoadBalancer > > see > https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.trunk.fulltest.java8/lastCompletedBuild/testReport/ > > I can replicate the MailMimeDecodeHeadersTest.testNonAsciiMailSubject > failure locally with maven (test passes when run in Eclipse), but I'm not > sure what is causing the failure. I haven't tried the other tests yet. > > > Am 02.11.2017 um 22:47 schrieb Apache Jenkins Server: >> >> The Apache Jenkins build system has built Camel.trunk.fulltest.java9 >> (build #983) >> >> Status: Still Failing >> >> Check console output at >> https://builds.apache.org/job/Camel.trunk.fulltest.java9/983/ to view the >> results. > > > -- Zoran Regvart
