[
https://issues.apache.org/jira/browse/FLINK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081897#comment-16081897
]
ASF GitHub Bot commented on FLINK-7141:
---------------------------------------
Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/4293
to be honest, I think the cache was used in the second build of the PR as
indicated by these lines (of the first build profile):
```
attempting to download cache archive - 3.41s
fetching
PR.4293/cache-linux-trusty-cd051817889efc5ff66a50de5c44d5db4ca23a5b661872a975c2c953f95d8ab6--jdk-oraclejdk8.tgz
found cache - 0.00s
adding /home/travis/.m2 to cache - 16.77s
```
Also, there, the cleanup (`test ! -d $HOME/.m2/repository/ || find
$HOME/.m2/repository/ -name "*.jar" -exec sh -c 'if ! zip -T {} >/dev/null ;
then echo "deleting invalid file: {}"; rm {} ; fi' \;`) took another 36s.
Strangely, in the non-cache build, I do not see any `Downloading:
.../maven-metadata.xml` or pom or jar file messages... my guess is that this is
due to the parameter
`-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn`?
- should we disable it for testing that there are actually no new downloads
with the cache in place?
> enable travis cache again
> -------------------------
>
> Key: FLINK-7141
> URL: https://issues.apache.org/jira/browse/FLINK-7141
> Project: Flink
> Issue Type: Improvement
> Components: Build System, Travis
> Affects Versions: 1.4.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
>
> In the past, we had some troubles with the travis cache but in general it may
> be a good idea to include it again to speed up build times by reducing the
> time the maven downloads take.
> This time, we should also deal with corrupt files in the maven repository and
> [tune
> travis|https://docs.travis-ci.com/user/caching/#Caches-and-build-matrices] so
> that it does not create corrupt caches in the first place.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
