action: encode the repo name in the SDK cache key #49
Conversation
The Zephyr SDK install has a step where it tweaks the library paths of the host utilities so match the full install path and have them run without having to set LD_LIBRARY_PATH. In the current setup that path includes the repository name, which means that if the repository is renamed the cached SDK is going to end up having a non working path leading to a confusing error, typically dtc not found. Make the repository name part of the SDK cache key, so that if the repository is renamed, the cached sdk with the wrong path is not reused. Signed-off-by: Fabio Baltieri <[email protected]>
fabiobaltieri
force-pushed
the
sdk-path
branch
from
16d8f54 to
8b7968e
Compare
|
cc @gmarull |
Just to understand the issue correctly - this only happens if you rename the GitHub repository after this action has been run at least once from a workflow under the old repository name? |
Yeah that's right. |
fabiobaltieri
merged commit c125c5e
into
zephyrproject-rtos:main
4 participants
The Zephyr SDK install has a step where it tweaks the library paths of the host utilities so match the full install path and have them run without having to set LD_LIBRARY_PATH. In the current setup that path includes the repository name, which means that if the repository is renamed the cached SDK is going to end up having a non working path leading to a confusing error, typically dtc not found.
Make the repository name part of the SDK cache key, so that if the repository is renamed, the cached sdk with the wrong path is not reused.