[
https://issues.apache.org/jira/browse/FLINK-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913165#comment-16913165
]
Chesnay Schepler commented on FLINK-13745:
------------------------------------------
Jup, that might be. However, it's just not feasible to allow so many different
versions in the cache, since each one adds about 1.3gb. Let's start with 1 and
see where this gets us.
> Flink cache on Travis does not exist
> ------------------------------------
>
> Key: FLINK-13745
> URL: https://issues.apache.org/jira/browse/FLINK-13745
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available, test-stability
> Time Spent: 10m
> Remaining Estimate: 0h
>
> More and more often I observe that Flink builds fail on Travis because of
> missing Flink caches:
> {code}
> Cached flink dir /home/travis/flink_cache/40072/flink does not exist. Exiting
> build.
> {code}
> It seems as if Travis cannot guarantee that a cache survives as long as the
> different profiles of a build are running. It would be good to solve this
> problem because now we have regularly failing builds:
> https://travis-ci.org/apache/flink/builds/572559629
> https://travis-ci.org/apache/flink/builds/572523730
> https://travis-ci.org/apache/flink/builds/571576734
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
