Closed glatterf42 closed 7 months ago
This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days.
This issue was closed because it has been inactive for 5 days since being marked as stale.
Hi everyone, please let me know if this is not the right place to report this issue/ask this question, but I don't quite know who else might be able to clarify this. Recently, our conda-forge CI tests started to fail (see here for the last successful run and here for the first failed one). These tests are run on the latest Windows and MacOS runner images that GitHub provides. While researching why the tests fail, I discovered that they were not using any cache despite being intended to. Here is the relevant part of our workflow file:
When running this workflow, even if the installation is successful, no cache is saved and I only receive the following error message:
Finally, here is the output that
conda info
produces during the run on Windows:And this is the one on MacOS:
Please note that this output is for Anaconda, but the same happens when using Miniconda. The run on Windows that produced this
conda info
output failed in the end while the one on MacOS was successful.One thing that I noted when looking at our workflow file is that the paths we provide for the cache action had not changed since they were introduced 3 years ago. Judging from the phrasing of the encountered error message, I think as soon as one of the paths provided for the cache action doesn't exist, no cache will be saved after successful execution of the workflow. Thus, I didn't expect our caching to work since the provided
Anaconda
paths would never be there for Miniconda and theappdata/local
path would never be there on Windows. I couldn't find any documentation for the$CONDA
environment variable either, but figured it would be better to remove that temporarily. This (and all subsequent tests) I did on iiasa/message_ix#715, which left me with~/.conda/pkgs
for the path provided to the cache action. Assuming that theconda info package cache
output lists all directories where packages that we might want cached are stored, I thought this path should be there for both Windows and MacOS. But I still received the same error message of non-existent paths. Next, I tried other options (always removing those that didn't work before):'**/_actions/iiasa/actions/main/setup-conda/*/pkgs'
and, due to #1125,'**/**/_actions/iiasa/actions/main/setup-conda/*/pkgs'
, but to no avail. I even tried hard-coding some paths for Windows:Still, I was told they didn't exist. So my question is: what am I missing here? Why is nothing being cached even if I provide paths to packages that conda itself tells me are used to store packages? And most importantly, how can I achieve caching for our workflow?
Please let me know if you need any further information. Many thanks in advance.