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?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
