Make this option default and reduce amount of details displayed by
twister.
This options has been enabled in CI for a while now with the intention
of making it default.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Update security policy documentation to indicate 4.2 is the latest
version, and drop 4.0 from the supported versions
Signed-off-by: Dan Kalowsky <dkalowsky@amperecomputing.com>
Signed-off-by: Daniel DeGrasse <ddegrasse@tenstorrent.com>
This commit updates the maintainer check workflow to use the zephyrbot "PR
assigner" token with `org:read` permission because the default workflow
token is not able to retrieve organisation-level user membership
information.
Note that the workflow trigger condition is changed from `pull_request` to
`pull_request_target` because non-workflow secrets may not be accessed from
`pull_request` trigger for security reasons.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
This commit updates the pull request assigner workflow to use the zephyrbot
token instead of the workflow token.
Note that the workflow token, by design, cannot access the
organisation-level user membership information, and may cause the assigner
script to return `Skip 'user': not in collaborators` even for valid
collaborators.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Doxygen 1.14 comes with really useful UX improvements which we want to
benefit from in our API documentation so update the CI job accordingly.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Use new docker with SDK 0.17.2.
SDK 0.17.2 has a new Qemu with improved support for RX architecture.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Python 3.10 and 3.11 are no longer supported so drop them from the
GitHub Actions test matrices.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Verify that collaborators/maintainers added to the MAINTAINERS.yml file
actually have access to the project and are members.
Only those who already gained access following the process shall be
added to the file.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Reduce frequency of counting issues. The output of this workflow is
legacy and published externally, so we should re-consider keeping this
or do things a bit differently.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
As time passes we are adding more babblesim tests which depend on code/
tests from tests/bluetooth just like we have many based on samples from
samples/bluetooth.
Let's also trigger the Babblesim CI job when anything changes in
tests/bluetooth, instead of trying to pinpoint the specific folders we
use, as otherwise every now and then we have coverage holes and issues
are introduced in main.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
The SDK is growing bigger and bigger, set the toolchain list so we only
fetch the ones needed by the tests we run, save some disk space,
apparently this workflow is getting close.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Now that we have faster runners, we can move this back to the night and
be productive during the day :)
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Remove the TSC approval requirements for binary blobs. Clarify
in the language that the submitter and reviewers shall ensure
that all binary blob requirements are being met before approval
and integration into Zephyr.
Signed-off-by: David Leach <david.leach@nxp.com>
Use a form based template instead of freesyle template. This will force
bug reporters to follow the template and provide the needed information
and will make triage easier and bug reports consistent.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Update to a revision of the manifest action that includes:
https://github.com/zephyrproject-rtos/action-manifest/pull/21
Also add the corresponding binary blobs labels parameters to the
workflow.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
GitHub seems to have issue with workflow state caching that causes the
DNM step to not work properly in few cases and not detecting changes in
the DNM tag, forcing people to mess with tags or close/opening PRs,
which in turns restarts all workflows.
Convert the script to Python so that the tag data is guaranteed to be
fresh.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Blackbox tests now shall include smoke tests,
that is Twister calls in the environment.
Additionally, those smoke tests will run
on multiple platforms.
Signed-off-by: Lukasz Mrugala <lukaszx.mrugala@intel.com>
This reverts commit 370e0882cb, the
condition is evaluated at workout creation time so this does not work at
all, plus some conditions don't have a label removal logic so pairing
this with the manifest run does not work anyway.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
The current CI setup sets the manifest DNM label in a workflow and
checks it in a different workflow. The one performing the check is
configured to rerun on label changes but it's been reported few times
that the rerun logic does not seem to always run effectively and there's
been cases where the manifest has been fixed but the label has not been
removed by the automation, resulting in a stale PR.
Since the manifest has its own dedicated label, fix this race condition
by checking for that label specifically in the manifest workflow rather
than in a separate one, this means that the check is always performed
after the script that sets the label.
It also means that on manifest changes the manifest step itself will
fail rather than the PR metadata check one.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Also trigger the bluetooth tests if tests/bluetooth/common/testlib/
is changed.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Use uv compile to generate requirements.txt from requirements.in
This works better to capture dependencies that work for multiple python
versions, not just the one that was used to generate the
requirements.txt file.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
We've previously restricted Blackbox test
runs to just one test file - test_output.py.
That was a mistake.
This commit makes the relevant workflow run
all of the blackbox test files again.
Signed-off-by: Lukasz Mrugala <lukaszx.mrugala@intel.com>
Updated the bsim-tests workflow to exclude all .rst files.
As per GitHub docs:
The order that you define paths patterns matters:
A matching negative pattern (prefixed with !) after a positive match
will exclude the path.
A matching positive pattern after a negative match will include the path
again.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
No functional change. This is only so as to adopt a versioning scheme
where the Zephyr version of the action is considered more recent than
the upstream version (here, v1.1.1) by means of using dots instead of
dashes.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Speed things up by using GH runners, we do not need the power of our own
runners to create the test plan. This also simplifies the workflow
considerably.
PRs now will get queued immediately, ie. no need to wait for a Zephyr
hosted runner to create the plan and then wait again for another round
to get more runners for execution.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
