Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CI: Zephyr, test against known working version and also the very latest on main #623

Merged
merged 2 commits into from
Oct 18, 2024
Merged

CI: Zephyr, test against known working version and also the very latest on main #623

merged 2 commits into from
Oct 18, 2024

Commits on Oct 18, 2024

  1. CI: reduce zephyr sdk install verbosity 

    Reduce the console output for the Zephyr sdk install.
This now matches the intent of libmetal but uses the documented wget
option.

Signed-off-by: Bill Mills <[email protected]>
    @wmamills
    wmamills committed Oct 18, 2024
    Configuration menu
    Copy the full SHA
    8b67185 View commit details
    Browse the repository at this point in the history

  2. CI: Do Zephyr build tests on known good and latest versions 

    Allow Zephyr testing to either use locked known good values
or the very latest versions.

This brings open-amp to parity with libmetal.  Open-amp did not have the
SDK URL discovery code so that was added here as part of this.

The known good versions are best for PR checking as if the build fails
it is almost always the PR itself that broke it.

The latest version is good for periodically checking compatibility with
the very latest Zephyr changes.

For now we run both on pushes and PRs.

We also run main against the latest zephyr check weekly as a look ahead.

Signed-off-by: Bill Mills <[email protected]>
    @wmamills
    wmamills committed Oct 18, 2024
    Configuration menu
    Copy the full SHA
    eced987 View commit details
    Browse the repository at this point in the history