Skip to content

Conversation

@ndechesne
Copy link
Contributor

No description provided.

It was incorrectly set (copy/paste) from kirkstone.

Signed-off-by: Nicolas Dechesne <[email protected]>
This is a cosmetic change, it seems better to have the runs-on section
earlier in the job definition.

Signed-off-by: Nicolas Dechesne <[email protected]>
We want to split the compile job matrix into two steps. In order to
avoid too much duplication of code, let's first isolate the compile
steps into a custom , local composite action. In the next commit, we
will split the matrix into two, and reuse the action.

Signed-off-by: Nicolas Dechesne <[email protected]>
The matrix jobs results in a large amount of jobs being started at the
same time. Running all jobs in parallel is not ideal to leverage the
OE sstate cache. For any common tasks (native, armv8, .. ) when the
object is missing from the sstate cache, it's likely going to be a
miss for several jobs. As a result, each of them will build the missed
object, and each of them will attempt to create the object in the
sstate cache.

Instead, with this change, we first build for the qcs8300 platform,
for both BSP variants. If these builds succeed we carry on with the other
machines/configs, with the hope that the sstate cache hit will be
better.

Signed-off-by: Nicolas Dechesne <[email protected]>
@ricardosalveti ricardosalveti merged commit 8349ec9 into qualcomm-linux:scarthgap Sep 3, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants