infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-17235) Possibly update java "latest11" on Jenkins
Date Sat, 10 Nov 2018 22:48:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-17235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin closed INFRA-17235.
-------------------------
    Resolution: Fixed

JDK 11.0.1 (build 13) installed and propagating out to all nodes now, should be completed
soon.

latest11 symlinked to it.

> Possibly update java "latest11" on Jenkins
> ------------------------------------------
>
>                 Key: INFRA-17235
>                 URL: https://issues.apache.org/jira/browse/INFRA-17235
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: CI
>            Reporter: John Roesler
>            Assignee: Gavin
>            Priority: Major
>
> Hi!
> I've been looking into why the PR builds in Apache Kafka have been failing with a high
frequency.
> Sorry in advance if this is a somewhat murky "issue", since a lot of the Kafka integration
tests are known to be flaky (aka, sensitive to timing issues). Timing-related failues are
reasonably common on Java 1.8, but since we started also running them on Java 11, it seems
to fail far more often than not.
> Specifically, I'm looking at this job: https://builds.apache.org/job/kafka-pr-jdk11-scala2.12/
> I happened to notice that the build is using:
> JAVA_HOME	/home/jenkins/tools/java/latest11
> which the https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix says
is using something called "jdk-11-ea+28", which sounds like an early-access version of java
11.
> I'm wondering if stability may be improved by updating it to the current released version,
11.0.1.
> Thanks,
> -John



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message