ci/ci: enable ccache by quaresmajose · Pull Request #2936 · qualcomm-linux/meta-qcom

Jose Quaresma (quaresmajose) · 2026-08-13T18:23:18Z

The ccache can improve significantly our builds speeds when we can't take
advantage of the bitbake sstate cache, in sutch scenario we need to compile
the code. The cache storage needs to be available from the previous builds
so we need to store these ccache artifacts temporay on our permanent storage.

Fixes #1051

Dmitry Baryshkov (lumag) · 2026-08-18T05:19:08Z

    INHERIT += "ccache"
    CCACHE_MAXSIZE = "200G"
    CCACHE_TOP_DIR = "${SSTATE_DIR}/ccache"
+    CCACHE_DISABLE = "1"


Can we just enable ccache for all the recipes? What are the drawbacks?

In internal discussions, we concluded that there wasn't much value in enabling it for everyone. However, the heavier packages in the compilation would always have some benefit. In reality, it's a trade-off between space occupied and benefit utilized.

there wasn't much value in enabling it for everyone

Why? What was the main argument for deciding it this way? Just to document it here. Do we have any stats?

We don't have stats and that conclusion came from a internal slack discussion.

Basically, we'll have to divide the available space among all existing components. Focusing a large portion of the allocated space on components that are fast enough even without ccache. We then conclude that it would be more efficient if we allocated space only to the components that take the most advantage of using ccache.

I'll add it to the commit.

Dmitry Baryshkov (lumag) · 2026-08-18T05:19:50Z

    CCACHE_DISABLE:pn-glibc = "0"
    CCACHE_DISABLE:pn-llvm = "0"
-    CCACHE_DISABLE:pn-linux-yocto = "0"
+    #CCACHE_DISABLE:pn-linux-yocto = "0"


So, what is in 2026-08-14 09:59:21 - INFO - | ERROR: Details can be found at: /work/build/tmp/work-shared/qcom-armv8a/kernel-source/.kernel-meta/cfg/merge_config_build.log ? Why does it fail?

I am in the evaluation process and I don't yet know the reasons.

It fails becuas it also requires the ccache-native for the native tools. After install ccache on the container and add the required configs it works

Isn't it a missing dependency somewhere?

The missing dependencie is HOSTTOOLS += "ccache"

That makes linux-yocto depend on the host's ccache, doesn't it? My point is that the recipe should be buildable even withou it, by using ccache-native.

github-actions · 2026-08-26T02:18:28Z

Test run workflow

Test jobs for commit `39cf185`

qcom-distro
Pass: 11 | Fail: 1 | Total: 12

qcom-distro_linux-qcom-6.18
Pass: 6 | Fail: 2 | Total: 8

nodistro
Pass: 10 | Fail: 0 | Total: 10

test-reporting-app · 2026-08-26T02:18:47Z

Test Results

30 files - 51 30 suites - 396 4h 12m 28s ⏱️ - 4h 3m 49s
13 tests - 160 9 ✅ - 143 0 💤 - 5 4 ❌ - 12
269 runs - 2 494 257 ✅ - 2 447 0 💤 - 29 12 ❌ - 18

For more details on these failures, see this check.

Results for commit 39cf185. ± Comparison against base commit faf4f4c.

This pull request removes 160 tests.

0_AudioRecord_Config01 ‑ AudioRecord_Config01
0_BT_FW_KMD_Service ‑ BT_FW_KMD_Service
0_GStreamer_Video_Encode_h264_480p ‑ GStreamer_Video_Encode_h264_480p
0_Libcamera_cam ‑ Libcamera_cam
0_Weston_Runtime_Preflight ‑ Weston_Runtime_Preflight
0_hotplug ‑ hotplug
10_AudioRecord ‑ AudioRecord
10_Docker_Kernel_Config ‑ Docker_Kernel_Config
10_Kubernetes_Kernel_Config ‑ Kubernetes_Kernel_Config
10_Logging_Journalctl_Validation ‑ Logging_Journalctl_Validation
…

♻️ This comment has been updated with latest results.

qcomlnxci · 2026-08-26T08:14:07Z

Test Coral run workflow

Test jobs for commit `28464f9`

qcomdistro: multimedia image-prop
Pass: 44 | Fail: 0 | Total: 44
qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9

Jose Quaresma (quaresmajose) · 2026-08-31T12:55:13Z

Proposed ccache to be installed on kas-container and it is accepted and available in :next image.

qcomlnxci · 2026-09-01T05:28:37Z

Test Coral run workflow

Test jobs for commit `2ca5572`

qcomdistro: multimedia image-prop
Pass: 36 | Fail: 0 | Total: 36
qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9

qcomlnxci · 2026-09-02T00:54:40Z

Test Coral run workflow

Test jobs for commit `5989d85`

qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9
qcomdistro: multimedia image-prop
Pass: 30 | Fail: 4 | Total: 34

Ricardo Salveti (ricardosalveti)

LGTM, but I believe we want to wait for kas 5.6, no?

Store the CCACHE_TOP_DIR inside the state-cache so we can access it from within the kas-container. Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

The ccache can improve significantly our builds speeds when we can't take advantage of the bitbake sstate cache, in such scenario we need to compile the code. The cache storage needs to be available from the previous builds so we need to store these ccache artifacts temporay on our permanent storage. Fixes qualcomm-linux#1051 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

We'll have to divide the available space among all existing components. Focusing a large portion of the allocated space on components that are fast enough even without ccache. We then conclude that it would be more efficient if we allocated space only to the components that take the most advantage of using ccache. Let's start with a short list of the heavier recipes; we'll adjust them as needed. A quick analysis of the buildstats of shows that the compilation time is high for this list of recipes. Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

The ccache it's saved within sstate-cache because it needs to be in a persistent storage location in order to be reused. Its management is private and therefore it should be excluded from the sstate-cache cleanup policy. Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

Jose Quaresma (quaresmajose) · 2026-09-10T16:52:05Z

I'm missing numbers in the commit about how much time it saves vs the amount of storage it adds

I don't have the exact numbers, but the more components that share the total space, the less space each one will have. Since less space results in less cache, then the more components, the less efficient it is.

Ricardo Salveti (ricardosalveti) · 2026-09-11T03:19:08Z

Should we wait for kas 5.6?

Jose Quaresma (quaresmajose) · 2026-09-11T08:32:52Z

We don't need to wait. There is a cosmetic update in kas-container and the essential package list in Dockerfile was updated to mach Yocto 6. The rest has no impact on us.

$ git diff --stat 5.5 origin/master 
 .github/actions/docker-init/action.yml   |  2 +-
 .github/actions/perform-tests/action.yml | 24 +++++++++++++-----------
 .github/workflows/next.yml               |  3 +--
 Dockerfile                               | 54 +++++++++++++++++++++++++++++++-----------------------
 docs/format-changelog.rst                |  2 +-
 kas-container                            |  4 ++--
 scripts/build-container.sh               |  4 ++--

Ricardo Salveti (ricardosalveti) · 2026-09-12T04:28:35Z

Known failures.

quic-yocto-ci · 2026-09-12T04:29:15Z

Backport failed for wrynose, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin wrynose
git worktree add -d .worktree/backport/2936-to-wrynose origin/wrynose
cd .worktree/backport/2936-to-wrynose
git switch --create backport/2936-to-wrynose
git cherry-pick -x 37fa5f8c3976bee2f15ca96a399d03a1dbf470fb 588e03d3976c8c3462613d724680bed3b8009e2d 5451b3dbea78682edc0b1d7c1e747fbb663c899c 35458a258f3015ddb9c5f4a8ee1d9776316fec9e 365630484461b5927ee7bd4d308efce239bcc88a 39cf1856083fe252efdaa789f9c696c032e10897

Ricardo Salveti (ricardosalveti) · 2026-09-12T04:29:35Z

Jose Quaresma (@quaresmajose) mind having a look at backporting to wrynose?

qcomlnxci · 2026-09-12T07:47:47Z

Test Coral run workflow

Test jobs for commit `39cf185`

qcomdistro: multimedia image-prop
Pass: 41 | Fail: 0 | Total: 41
qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9

Jose Quaresma (quaresmajose) · 2026-09-12T20:41:08Z

Jose Quaresma (Jose Quaresma (@quaresmajose)) mind having a look at backporting to wrynose?

Proposed in #3144

Description Backport of #2936 to wrynose.

It avoids reproducibility problems and is recommended by good security practices. Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

Proposed ccache to be installed on kas-container and it is accepted and available in the image. The change landed in master 5.5-9-g0555188 Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

It avoids reproducibility problems and is recommended by good security practices. Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

Proposed ccache to be installed on kas-container and it is accepted and available in the image. The change landed in master 5.5-9-g0555188 Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

It avoids reproducibility problems and is recommended by good security practices. Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

Proposed ccache to be installed on kas-container and it is accepted and available in the image. The change landed in master 5.5-9-g0555188 Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

It avoids reproducibility problems and is recommended by good security practices. Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

Proposed ccache to be installed on kas-container and it is accepted and available in the image. The change landed in master 5.5-9-g0555188 Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

Partial port of meta-qcom: github/workflows: extract kas-container from the image Backport from qualcomm-linux/meta-qcom#2934 ci/ci: enable ccache Backport from qualcomm-linux/meta-qcom#2936

It avoids reproducibility problems and is recommended by good security practices. Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com> (cherry picked from commit e6bb390)

Proposed ccache to be installed on kas-container and it is accepted and available in the image. The change landed in master 5.5-9-g0555188 Backport from qualcomm-linux/meta-qcom#2936 Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com> (cherry picked from commit fac2470)

Jose Quaresma (quaresmajose) requested review from Dmitry Baryshkov (lumag), Milosz Wasilewski (mwasilew), Nicolas Dechesne (ndechesne) and Ricardo Salveti (ricardosalveti) as code owners August 13, 2026 18:23

Jose Quaresma (quaresmajose) force-pushed the ccache branch from 8b220d0 to 7a9da88 Compare August 14, 2026 09:32

Jose Quaresma (quaresmajose) marked this pull request as draft August 14, 2026 11:30

Dmitry Baryshkov (lumag) requested changes Aug 18, 2026

View reviewed changes

Jose Quaresma (quaresmajose) force-pushed the ccache branch 2 times, most recently from 227959f to 28464f9 Compare August 25, 2026 15:51

Dmitry Baryshkov (lumag) reviewed Aug 25, 2026

View reviewed changes

Comment thread ci/ccache.yml

Jose Quaresma (quaresmajose) force-pushed the ccache branch 2 times, most recently from d504013 to 2ca5572 Compare August 31, 2026 12:52

Jose Quaresma (quaresmajose) force-pushed the ccache branch from 2ca5572 to 702291f Compare September 1, 2026 10:03

Jose Quaresma (quaresmajose) marked this pull request as ready for review September 1, 2026 10:04

Jose Quaresma (quaresmajose) requested review from Anuj Mittal (anujm1), Koen Kooi (koenkooi) and Viswanath Kraleti (vkraleti) as code owners September 1, 2026 10:04

Jose Quaresma (quaresmajose) force-pushed the ccache branch from 702291f to 5989d85 Compare September 1, 2026 10:10

Dmitry Baryshkov (lumag) added the backport wrynose label Sep 2, 2026

Dmitry Baryshkov (lumag) previously approved these changes Sep 2, 2026

View reviewed changes

Comment thread ci/ccache.yml

Jose Quaresma (quaresmajose) dismissed Dmitry Baryshkov (lumag)’s stale review via d8fe1b8 September 2, 2026 08:23

Jose Quaresma (quaresmajose) force-pushed the ccache branch from 5989d85 to d8fe1b8 Compare September 2, 2026 08:23

Dmitry Baryshkov (lumag) previously approved these changes Sep 2, 2026

View reviewed changes

Ricardo Salveti (ricardosalveti) previously approved these changes Sep 2, 2026

View reviewed changes

Jose Quaresma (quaresmajose) added 4 commits September 10, 2026 17:46

ci: add KAS configuration for ccache

5451b3d

Store the CCACHE_TOP_DIR inside the state-cache so we can access it from within the kas-container. Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>

Jose Quaresma (quaresmajose) force-pushed the ccache branch from f16a384 to 39cf185 Compare September 10, 2026 16:47

Ricardo Salveti (ricardosalveti) approved these changes Sep 12, 2026

View reviewed changes

Ricardo Salveti (ricardosalveti) merged commit 87cec8c into qualcomm-linux:master Sep 12, 2026
241 of 242 checks passed

Jose Quaresma (quaresmajose) deleted the ccache branch September 12, 2026 20:37

Jose Quaresma (quaresmajose) mentioned this pull request Sep 12, 2026

[Backport wrynose] ci/ci: enable ccache #3144

Merged

Dmitry Baryshkov (lumag) added a commit that referenced this pull request Sep 13, 2026

[Backport wrynose] ci/ci: enable ccache (#3144)

5ac671e

Description Backport of #2936 to wrynose.

Jose Quaresma (quaresmajose) mentioned this pull request Sep 14, 2026

Port CI changes from meta-qcom: kas-container and ccache qualcomm-linux/meta-qcom-distro#468

Merged

Uh oh!

Conversation

Jose Quaresma (quaresmajose) commented Aug 13, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Aug 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test run workflow

Test jobs for commit 39cf185

Uh oh!

test-reporting-app Bot commented Aug 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test Results

Uh oh!

qcomlnxci commented Aug 26, 2026

Test Coral run workflow

Test jobs for commit 28464f9

Uh oh!

Jose Quaresma (quaresmajose) commented Aug 31, 2026

Uh oh!

qcomlnxci commented Sep 1, 2026

Test Coral run workflow

Test jobs for commit 2ca5572

Uh oh!

Uh oh!

qcomlnxci commented Sep 2, 2026

Test Coral run workflow

Test jobs for commit 5989d85

Uh oh!

Ricardo Salveti (ricardosalveti) left a comment

Choose a reason for hiding this comment

Uh oh!

Jose Quaresma (quaresmajose) commented Sep 10, 2026

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 11, 2026

Uh oh!

Jose Quaresma (quaresmajose) commented Sep 11, 2026

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 12, 2026

Uh oh!

Uh oh!

quic-yocto-ci commented Sep 12, 2026

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 12, 2026

Uh oh!

qcomlnxci commented Sep 12, 2026

Test Coral run workflow

Test jobs for commit 39cf185

Uh oh!

Jose Quaresma (quaresmajose) commented Sep 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

github-actions Bot commented Aug 26, 2026 •

edited

Loading

Test jobs for commit `39cf185`

test-reporting-app Bot commented Aug 26, 2026 •

edited

Loading

Test jobs for commit `28464f9`

Test jobs for commit `2ca5572`

Test jobs for commit `5989d85`

Test jobs for commit `39cf185`