Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/4293
Looks like with the cache it is only downloading flink artefacts from
earlier versions for API comparisons (I excluded
`$HOME/.m2/repository/org/apache/flink/` from the cache).
Also, it seems there is no real performance gain from using the cache :( or
at least the influence of the differences in the runtime of the tests is bigger
so that the cache's influence is inconclusive.
With the control over deleting corrupt caches ourselves, we could skip the
.m2 repo cleanup and save another 30s there. In the end, we don't know whether
corrupt repositories were caused by Travis or Maven - the settings in this PR
should fix the former and the repo cleanup the latter. We could thus try
removing the latter once we can delete caches ourselves.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
