Skip to content

Conversation

@lupyuen
Copy link
Member

@lupyuen lupyuen commented Oct 17, 2024

Summary

When we submit or update a Complex PR that affects All Architectures (Arm, RISC-V, Xtensa, etc): CI Workflow shall run only half the jobs. Previously CI Workflow will run arm-01 to arm-14, now we will run only arm-01 to arm-07.

When the Complex PR is Merged: CI Workflow will still run all jobs arm-01 to arm-14

Simple PRs with One Single Arch / Board will build the same way as before: arm-01 to arm-14

This is explained here: apache/nuttx#14376

Note that this version of arch.yml has diverged from nuttx repo, since we are unable to merge apache/nuttx#14377

Impact

When we submit or update a Complex PR: CI Workflow shall run only half the jobs: arm-01 to arm-07 (instead of arm-01 to arm-14)

No changes to the CI Workflow when we merge a Complex PR. No impact for Simple PRs.

Testing

Creating a Simple PR will run jobs arm-01 to arm-14 (like before)
https://github.com/lupyuen5/label-nuttx/actions/runs/11380165777

Creating a Complex PR will only run jobs arm-01 to arm-07 (skipping arm-08 to arm-14)
https://github.com/lupyuen5/label-nuttx/actions/runs/11380214455

Merging a Complex PR will run all jobs arm-01 to arm-14 (like before)
https://github.com/lupyuen5/label-nuttx/actions/runs/11380246952

When we submit or update a Complex PR that affects All Architectures (Arm, RISC-V, Xtensa, etc): CI Workflow shall run only half the jobs. Previously CI Workflow will run `arm-01` to `arm-14`, now we will run only `arm-01` to `arm-07`.

When the Complex PR is Merged: CI Workflow will still run all jobs `arm-01` to `arm-14`

Simple PRs with One Single Arch / Board will build the same way as before: `arm-01` to `arm-14`

This is explained here: apache/nuttx#14376

Note that this version of `arch.yml` has diverged from `nuttx` repo, since we are unable to merge apache/nuttx#14377
Copy link
Contributor

@cederom cederom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @lupyuen lets see how this improves the situation :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[URGENT] Reducing our usage of GitHub Runners

2 participants