Closed rturrado closed 8 months ago
I'm going to close this issue because the conan remove
step went from being something we thought we shouldn't need, to something we wanted to force on self-hosted runners (slash containers).
Because self-hosted runners seem to kind of save a state between runs (what doesn't happen with GitHub-hosted runners, where every run starts from a clean environment).
We think that this job, from
assets.yml
, is trying to reuse the Conan cache from previous runs (this is already weird, because GitHub Actions jobs should be supposed to run in a clean fresh environment). And, in doing so, it fails to find the wheel binary.So the idea for a possible fix for this issue would be to put the wheel binary in the same place as the rest of the Conan package binaries. We believe that this is not done at the moment because
setup.py
uses thislibqasm/*:python_dir
parameter, and it places the wheel binary there.Looking a bit now into the code, I would say both
cbuild_dir
anddist_dir
have no much meaning when using Conan, as everything should go into the Conan package.