Skip to content

Commit

Permalink
ci: yocto-check-layer: run KAS with debug
Browse files Browse the repository at this point in the history
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.

Signed-off-by: Nicolas Dechesne <[email protected]>
  • Loading branch information
ndechesne committed Nov 26, 2024
1 parent ab75ac6 commit 5a9c8ac
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
6 changes: 3 additions & 3 deletions .github/workflows/build-yocto.yml
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ jobs:
- uses: actions/download-artifact@v4
with:
name: kas-lock
path: ci/*.lock.yml
path: ci/

- name: Run yocto-check-layer
run: |
Expand All @@ -59,7 +59,7 @@ jobs:
- uses: actions/download-artifact@v4
with:
name: kas-lock
path: ci/*.lock.yml
path: ci/

- name: Run Yocto patchreview
run: |
Expand All @@ -85,7 +85,7 @@ jobs:
- uses: actions/download-artifact@v4
with:
name: kas-lock
path: ci/*.lock.yml
path: ci/

- name: Kas build
run: |
Expand Down
2 changes: 1 addition & 1 deletion ci/yocto-check-layer.sh
Original file line number Diff line number Diff line change
Expand Up @@ -22,4 +22,4 @@ CMD="$CMD --no-auto-dependency"
CMD="$CMD --machines $(echo $(find $TOPDIR/conf/machine/ -maxdepth 1 -name *.conf -exec basename {} .conf \; ))"

echo "Running kas in $KAS_WORK_DIR"
exec kas shell $TOPDIR/ci/base.yml --command "$CMD"
exec kas -l debug shell $TOPDIR/ci/base.yml --command "$CMD"

0 comments on commit 5a9c8ac

Please sign in to comment.