@Michal
The arm64 cache is separated at the moment. However, I found there might be something wrong on uploading the arm64 cache after successful building. You can find “md5deep command not found” on arm64 if you check and click the report at line: 5152 (store build cache) . This is different from amd64 report at line 3550
In my project, the cache would not take effect in travis at the moment on arm64 lxd container.
Given that this was not the first time the cache broke on travis, would it be appropriate to add some kind of internal tests to ensure caching works before changes are applied in production?
For language: python builds on the arm64, s390x, and ppc64le archs we get a permission error for the cache when pip tries to build a wheel (specifically numpy and coverage in our case, but probably any wheel):
Building wheels for collected packages: numpy, coverage
WARNING: Building wheel for numpy failed: [Errno 13] Permission denied: '/home/travis/.cache/pip/wheels/04'
WARNING: Building wheel for coverage failed: [Errno 13] Permission denied: '/home/travis/.cache/pip/wheels/43'
Failed to build numpy coverage
ERROR: Could not build wheels for numpy which use PEP 517 and cannot be installed directly
The command "pip install --upgrade -r requirements.txt" failed and exited with 1 during .
Your build has been stopped.