XCC doesn't like having quotes in the section name, so
workaround it by overriding __in_section_unique_named()
similar to __in_section_unique().
Signed-off-by: Daniel Leung <daniel.leung@intel.com>

Zephyr device that is not a GATT Client, should ignore indication.

An Android device may send an indication even if Zephyr
device does not support GATT Client role. In that case, the sent
error response was improperly matched to subsequent GATT request
of the Android device which caused issues.
Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>

The task_wdt was getting stuck after approx. 36 hours on e.g. nRF52840,
which has a SysTick with 32768 Hz. This corresponds to an overflow of
the uint32_t current_ticks in schedule_next_timeout.

This commit fixes the accidentally introduced narrowing conversion.

Fixes #40152
Signed-off-by: Martin Jäger <martin@libre.solar>

PR #39980 added qsort to minimal libc but caused
shell_modules sample to fail building.
Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>

We now cleanup at the beginning.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Check if test plan exist before trying to read it.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Merged 3 files used to generate the test plan per PR based on the
changes. 2 python scripts and a shell script are now all merged into 1
python script that generates the input file for twister based on a list
of changed files by the PR.

This remove lots of old and obsolete code and simplifies things a bit,
no need anymore for an intermediate script to call twister, we call it
directly in the workflow and use the new test_plan script to generate
the test plan.

This also reenables the recently disabled tag based filtering which had
a bug, bug is resolved in this new implementation.

On push events, we now run twister without the --integration option to
catch any issues in the main branch that were not caught in PRs. PRs
continue to run with --integration enabled. This event (push) is now run
on 15 builders due to the increased size.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Update CI docs and the badge with links pointing to GH actions rather
than buildkite.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Adapt events and cron to the 2.7 branch.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Cancel using GH runner for faster execution.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Add branch name to the ccache key to avoid cache contamination from old
branches.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

This action replaces current buildkite workflow and uses github actions
to build and run tests in the zephyr tree using twister. The main
differences to current builtkite workflow:

- the action handles all 3 events: pull requests, push and schedule

- the action determines size of matrix (number of build hosts) based on
  the change with a minimum of 1 builder. If more tests are built/run
  due to changes to boards or tests/samples, the matrix size is
  increased. This will avoid timeouts when running over capacity due to
  board/test changes.

- We use ccache and store cache files on amazon S3 for more flexibility

- Results are collected per build host and merged in the final step and
  failures are posted into github action check runs.

- It runs on more powerful instances that can handle more load.
  Currently we have 10 build hosts per run (that can increase depending
  on number of tests run) and can deliver results within 1 hour.

- the action can deal with non code changes and will not allocate more
  than required to deal with changes to documentation and other files
  that do not require running twister

The goal long-term is better integrate this workflow with other actions
and not run unncessarily if other workflows have failed, for example, if
commit message is bogus, we should stop at that check, to avoid wasting
resources given that the commit message will have to be fixed anyways
which would later trigger another run on the same code.

Currently there is 1 open issue with this action related to a github
workflow bug where the final results are not posted to the same workflow
and might appear under other workflows. Github is working on this bug.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

In case of MSIS selected as system clock source it is necessary
to set Voltage scaling (VOS) when freqency is greater than 24MHz
Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

When MSI trimming values where set to 0,
and MSIS is used as system core clock and MSI > 4 MHz,
it causes uart to fail.
There is no need to set thoses trimming values.
So keep the default reset value. (keep ST Factory calibration)
Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

Because on stm32u5 MSIS is the default clock after reset,
changing MSIS range means immediate frequency change.
Thus it is important to do it after flash latency change
in case of higher new frequency.
Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

Missing definition of STM32_SYSCLK_SRC_MSIS
especially needed for STM32U5
Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

Sets SID in bt_le_per_adv_sync_recv_info when host receives
a Periodic Advertising Report
Signed-off-by: Johan Lundin <johan.lundin@nordicsemi.no>

This fix not being able to re-connect channel after disconnect.
Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>

If an LTK or an STK is available and encryption is required
(LE security mode 1) but encryption is not enabled, the
service request shall be rejected with the error code
"Insufficient Encryption".

This is affecting L2CAP/LE/CFC/BV-25-C and L2CAP/ECFC/BV-32-C
qualification test cases.
Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>

Many tests and CI activties are being missed by excluding tests
mistakingly when running twister.
This is visibile when you change one or more tests in kernel/ for
example, twister does not run those tests that have changed at all and
marking the PR as tested and ready to be merged.

Temporary fix for #40235.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Otherwise reporting is skipped and failures are not recorded.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Use ccache to speed up builds.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Retry west when update fails and use update.narrow configuration.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Add missing ")".
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Avoid rebasing and instead use the commit range. This avoids issues with
trees having intermediate rebase data after a reboot (due to
cancellation).
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Run code coverage reporting on main zephyr repo only.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

To avoid conflicts in reporting.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Use released version instead of master.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Namespace job names and retry west update if something goes wrong the
first time.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Rename to make action file name obvious referring to bluetooth, rather
than the tool used.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Misc fixes including:
- unique job names
- Change description to mention Bluetooth
- Retry west update
- Use latest unit test publication action
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

No need to run on weekends, nothing much happens, so lets save some
resources.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Fix a minor typo in action and always set variable controlling reports.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Configure git for rebase by setting user name, email.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

- use zephyr runner
- reduce number of builders and adapt matrix to be platform based
- check for changed files and optimize run accordingly, should reduce
  build times depending on what has changed
- If no source has changed, skip twister completely.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Add a code coverage collection action that triggers based on a schedule
on the main branch and posts results to

 https://app.codecov.io/gh/zephyrproject-rtos/zephyr

Signed-off-by: Anas Nashif <anas.nashif@intel.com>

Disable CAN bus tests since can1 is disabled by default due to an IRQ
conflict with the USB controller.
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>

LwM2M was not covered by networking build all test, leaving an opening
for possible regression in modules that are not enabled by default in
the sample.
Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>

`engine_remove_observer_by_path()` was not updated during some recent
LwM2M observer changes, still using the `engine_observer_list` which got
moved into the `lwm2m_context` structure. Update the function to align
with these changes.
Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>

With the maximum number set to 20, the sample fails to build for
both platforms set as allowed for this sample and mentioned in its
documentation, i.e. 96b_carbon_nrf51 and nrf51dk_nrf51422 (a build
attempt ends up with an SRAM region overflow). Use a lower number
to prevent this failure and set both those boards as integration
platforms, so that such problem, if it was to appear again, could be
caught by CI.
Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>