The problem is not that bad stuff is in the cache (which is the only
thing a cache cleaning solves), it is that the test stages don't
download the correct one.
Our compile stage uploads stuff in to the cache, and the subsequent test
builds downloads it again.
Whether the upload from the compile phase is visible to the test phase
is basically a timing thing; it depends on the visibility guarantee that
the backing infrastructure provides. So far it _usually_ worked, but
these are naturally things that may change over time.
On 18/06/2019 09:20, Jeff Zhang wrote:
If it is travis caching issue, we can file apache infra ticket and ask them
to clean the cache.
Chesnay Schepler <ches...@apache.org> 于2019年6月18日周二 下午3:18写道：
This is (hopefully a short-lived) hiccup on the Travis caching
infrastructure.
There's nothing we can do to _fix_ it; if it persists we'll have to
rework our travis setup again to not rely on caching.
On 18/06/2019 08:34, Kurt Young wrote:
Hi dev,
I noticed that all the travis tests triggered by pull request are failed
with the same error:
"Cached flink dir /home/travis/flink_cache/xxxxx/flink does not exist.
Exiting build."
Anyone have a clue on what happened and how to fix this?
Best,
Kurt
