ci: yocto-check-layer: run KAS with debug #91
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ndechesne
requested review from
quaresmajose,
ricardosalveti and
sbanerjee-quic
as code owners
When using download-artifact action, the path attribute is the destination path, and it was wrongly set to ci/*.lock.yaml. As a result, the lock files were extracted in meta-qcom-hwe/ci/*.lock.yaml/ folder instead of meta-qcom-hwe/ci. Signed-off-by: Nicolas Dechesne <[email protected]>
quaresmajose
approved these changes
Nov 26, 2024
There was a problem hiding this comment.
LGTM,
I have tried something like that in my first approach. but then I got confused after the review.
#36 (comment)
Thanks for fixing
ricardosalveti
approved these changes
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some reasons, kas does not checkout what we expect. The lock yaml files contain the most recent commits from poky and meta-qcom, which is expected since we run kas dump --update, however the downstream kas commands checkout the latest commits in the local mirror, not what we set in the lock files.
Let's add some debug to observe what is happening during the build.