This workflow runs in the background and does not report anything and
does emit failures. Remove for now until we have something that is
actionable.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit updates the CI workflows to use the CI image v0.26.7, in order
to pull in the Zephyr SDK 0.16.5 release.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Seems like GitHub introduced a macOS on ARM runner, add it to the
multiplatform test, with this we are running all the SDKs minus the
Linux ARM64 one.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Align the standard action versions with the other workflows, those have
been updated in 0dcb0518be but this file was merged after.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
gcovr 7.0 has some incompatible format, stick with 6.0 for now until we
have a compatible solution with gcovr 7.0 output.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Pytest twister harness tests have been added to the
twister_tests.yml workflow some time ago.
However, the $ZEPHYR_BASE/scripts/pylib/pytest-twister-harness/**
has not been monitored by the automatic GitHub Action triggers
of that workflow.
This change adds monitoring for the relevant files.
Signed-off-by: Lukasz Mrugala <lukaszx.mrugala@intel.com>
Update Github actions to their latest versions to fix the following
warnings on runs:
```
Node.js 16 actions are deprecated. Please update the following actions
to use Node.js 20: actions/checkout@v3, actions/cache@v3,
actions/upload-artifact@v3. For more information see:
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
```
`actions/checkout` and `actions/cache` are straight Node version
upgrades, `actions/upload-artifact` and `actions/download-artifact` have
breaking changes, but don't appear to affect our usage.
https://github.com/actions/upload-artifact
Signed-off-by: Jordan Yates <jordan.yates@data61.csiro.au>
Add a new workflow to build the hello world sample application on all
three supported platforms using the reusable setup action.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Get more reviewers added to make sure we have all relevant reviewers
looking at changes targeting collab branches.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
We should not have any dependencies on optional modules, for example on
Kconfigs from optional modules. Compliance has to pass without any
optional modules enabled.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
The ZEPHYR_SDK_INSTALL_DIR currently tries to read the SDK_VERSION at
the PR base ref, but this has only been introduced recently. Move the
ZEPHYR_SDK_INSTALL_DIR settings down as part of the build step after the
rebase so the file will always be found from now, even on old PRs.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Drop all hardcoded ZEPHYR_SDK_INSTALL_DIR settings, set the variable
automatically from the SDK_VERSION file instead.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Add new workflow steps to the babblesim workflow to run
also the UART tests on the nrf52_bsim.
This commit:
* Enables the single device tests (which we may
move to the normal twister workflow once we fix the
requirement for a fixture)
* Adds as a placeholder the infra for multidevice tests.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
A simple workflow that runs when a PR is merged and updates the
elasticsearch index with merged PR info.
The dashboard for displaying the information can be found here:
https://kibana.zephyrproject.io/
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Needed for full functionality of the job server in twister
which only works with kitware supplied ninja version.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Add "Architecture Review" and "dev-review" to the list of labels that
block a PR from merging, less chances to merge these before discussion
unintentionally.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Increase stack size for tests and exclude nono libc scenarios causing
some issues with coverage collection.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Use gcovr to generate reports and upload cobertura style file instead of
previously lcov info file.
We have been seeing issues with lcov format and code being reporting as
not covered although by inspecting the generate output files, they
should be.
The XML format we generate is otherwise easier to parse and deal with.
Also reduce frequency to twice a day.
Fixes#66656
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Switch from native_posix to native_sim as test platform
for this workflow.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Switch from native_posix to native_sim as test platform
for this workflow.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Add a step to the first twister shard to upload the list of Python
packages used with the build.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
This fixes a bug with the action's Docker container apparently not being
able to run Node correctly anymore...
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Coverity issues need to be resolved and closed by owners, not by the
bot. Other wise we will continue scanning them and reporting them over
and over.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Seems like the PDF build hit the "detected dubious ownership in
repository" issue that has already been worked around in other workflow.
Add that step here as well.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Skip the rebase step if it's not a pull request. Schedule and push runs
have no base ref to rebase against anyway, currently the step is failing
and being skipped.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Hardwaremap testing requires installing requirements-run-tests.txt.
This change adds that to the relevant workflow.
Signed-off-by: Lukasz Mrugala <lukaszx.mrugala@intel.com>
Also run some split BT stack tests on the nrf5340 platform
to test this configuration.
Move the selection of which BT tests are built and run
in each platform to files in the tests/bsim/ folder.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
The compliance and coding guidelines workflows are using the same pip
cache key, but they install a different set of packages. This is
probably a copy paste error from the documentation build workflow, which
has been changed to use a hash, and is causing one of the two steps to
restore from a incorrect cache.
Fix this by using a hash of the workflow file itself as a key, as that's
where the python package list is defined.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Add some west update flags to do a shallow fetch of the modules and
skip the tags. That data is not needed anyway, should make the
compliance check initialization a bit faster.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
The license check workflow quietly stopped working after commit
8f66f854c3. Upgrading the checkout action
changed default behavior to only fetch one commit instead of all history
for all branches, which caused an uncaught fatal error in the scancode
action:
fatal: ambiguous argument 'origin/main..': unknown revision or path not
in the working tree.
The scancode action then completed successfully having not actually
checked anything.
Fix this by setting the checkout action fetch depth to 0, similar to
other workflows.
Signed-off-by: Maureen Helm <maureen.helm@analog.com>
As documentation is now built using one of our self-hosted runners,
have the GitHub action only run for the upstream repo, not for potential
forks.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Upgrade to v1.2.0, which comes with a bugfix and support for processing
PRs that have removed modifications to the manifest.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
looks like our docker image is way too big for the GH runners, so move
to own runners until we have a better solution.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
PR #63195 has managed to change code under test without
triggering those tests.
This change should remedy that by creating a new workflow,
based on twister_tests.yaml, that runs tests in
scripts/tests/build_helpers if build_helpers are modified.
Such a workflow should be easily extendable if we ever have more
non-Twister things to test in scripts/pylib.
Signed-off-by: Lukasz Mrugala <lukaszx.mrugala@intel.com>
Run all bsim bluetooth controller tests also
on a nrf5340bsim_nrf5340_cpunet, as the controller
runs in a quite different mode.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Anas Nashif