flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maximilian Michels <...@apache.org>
Subject Re: Failing Builds on Travis
Date Tue, 28 Apr 2015 11:49:01 GMT
Hi Robert,

Thanks for investigating the Travis build issues. I'm very much in favor
for dropping Java 6. It's deprecated. All major Linux distributions are
shipping at least Java 7. It's a rare use case that requires a lot of
effort for us to maintain backwards compatibility.

I don't recall the discussion but if we really decided to keep Java 6, then
I guess we have to install a custom Maven version on Travis.


On Tue, Apr 28, 2015 at 1:34 PM, Robert Metzger <rmetzger@apache.org> wrote:

> Hi,
> looking at the last builds on Travis, you'll notice that our builds are in
> a pretty bad state: https://travis-ci.org/apache/flink/builds.
> It seems that the last 15 builds on master all failed.
> These are the errors I saw + their status:
> - Deadlock during cache up/download: I asked travis and they suggested a
> workaround that I'm currently testing (MALLOC_ARENA=2, in master)
> - issues opening zip files: The problem there is that some jars in the
> cache seem to be corrupt. I asked ASF Infra to delete all caches, they did
> it already, so the problem should be resolved.
> - Maven failing on the java6 builds. The issue is that Travis updated their
> build environment (April update [1]), which included a version upgrade of
> Maven from 3.2.5 to 3.3.1. As per Maven 3.3.1, they are not supporting Java
> 6 anymore [2].
> It seems that travis is rolling back the April environment updates [3] so
> the issue will probably disappear for a few days until they fixed their
> environment update.
> We can resolve the issue by two ways a) drop Java6 support, b) manually
> install maven on travis (its a matter of 1-2hrs).
> - The third build on travis (hadoop200-alpha) is failing due to some Flink
> tests: https://travis-ci.org/apache/flink/jobs/60335907
> It would be good if somebody who worked on this recently could take a
> closer look.
> Please let me know how you want to fix the Java6/Maven issue!
> a) Drop Java 6 support for Flink
> b) Use an older Maven version for now.
> I'm in favor of option b) because the community recently decided to keep
> Java6 support. (Fun fact: Java 7 reached its end of support lifecycle [4]
> in April 2015)
> Robert
> [1] http://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
> [2] https://issues.apache.org/jira/browse/MNG-5780
> [3] https://twitter.com/traviscistatus/status/592902357144498176
> [4]
> http://en.wikipedia.org/wiki/Java_version_history#Java_SE_7_.28July_28.2C_2011.29

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message