Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CMake configuration step fails after workers update

See original GitHub issue

Hi, I’ve set up GitHub workflow with run-cmake and 5 days ago it did work fine. Right now configuration step fails on macos-latest runner with the following error:

CMake Error: The current CMakeCache.txt directory /Users/runner/runners/2.263.0/work/chessx/b/ninja/CMakeCache.txt is different than the directory /Users/runner/runners/2.262.1/work/chessx/b/ninja where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt
25
  CMake Error: The source "/Users/runner/runners/2.263.0/work/chessx/chessx/CMakeLists.txt" does not match the source "/Users/runner/runners/2.262.1/work/chessx/chessx/CMakeLists.txt" used to generate cache.  Re-run cmake with a different source directory.

Judging from path mismatches it appears that worker infrastructure has been updated. However where did CMakeCache.txt with old path come from? Is there any caching going on in run-cmake?

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

erysajcommented, Jun 4, 2020

I guess warning about existing build directory is spot on; silently cleaning the directory is likely to mask user’s mistake

0reactions

lukkacommented, Jun 4, 2020

No problem, happy to help. The ‘dir’ step indeed revealed the presence of CMakeCache.txt file in the build directory pointed by the argument of CMake. I think the ‘run-cmake’ action could to delete the content of the build directory, or at least warn about the presence of an existing CMakeCache.txt.