Go to file
Daniel Leung b2f3d801b4 twister: pytest: use test timeout as the default base timeout
The default base timeout for pytest is statically set by
the TwisterHarnessConfig class to be 60 seconds. However,
sometimes it takes longer than 60s before the app starts
to run, especially on emulator/simulator where it takes
quite some time to start. So pass the test timeout as
the base timeout via pytest command line argument.

Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2024-07-27 15:18:01 +03:00
.github ci: compliance: add a PR description check step 2024-07-11 18:37:09 -04:00
arch arch: riscv: remove PMP stack guard for stack overflow handler 2024-07-27 15:12:25 +03:00
boards boards: riscv: neorv32: Add platform and model name 2024-07-27 15:14:46 +03:00
cmake toolchain: arcmwdt: don't set STDC_LIB_EXT1 macro in case of minimal libc 2024-07-12 09:34:58 -04:00
doc doc: release: Finalize v3.7.0 release notes and migration guide 2024-07-26 13:17:55 +02:00
drivers drivers: gnss: remove dangerous loop 2024-07-27 15:17:52 +03:00
dts modules: hal_nordic: Support EGU130 driver instance 2024-07-27 15:15:07 +03:00
include/zephyr posix: posix_types.h: simplify conditions on pthread types 2024-07-27 15:17:24 +03:00
kernel device: remove const qualifier from node label copy 2024-07-27 15:09:10 +03:00
lib lib: os: change __printk_get_hook return type to printk_hook_fn_t 2024-07-27 10:41:01 +03:00
misc cmake: modules: dts: use devicetree stub file 2023-10-20 12:18:17 -07:00
modules modules: hal_nordic: Support EGU130 driver instance 2024-07-27 15:15:07 +03:00
samples samples: bluetooth: minor logging changes in PAwR samples 2024-07-27 15:14:37 +03:00
scripts twister: pytest: use test timeout as the default base timeout 2024-07-27 15:18:01 +03:00
share sysbuild: check for existence of APPLICATION_CONFIG_DIR 2024-06-27 10:58:11 -04:00
snippets snippets: nus-console: doc: Remove invalid device-tree requirements 2024-07-25 09:26:20 +02:00
soc modules: hal_nordic: Support EGU130 driver instance 2024-07-27 15:15:07 +03:00
submanifests submanifests: update tflite-micro 2024-06-28 07:50:12 -04:00
subsys net: utils: improve hex digit character checking in net_bytes_from_str 2024-07-27 15:16:42 +03:00
tests tests: posix: net: open native_sim in c++,posix,net,native case 2024-07-27 15:17:24 +03:00
.checkpatch.conf checkpatch: ignore EXPORT_SYMBOL 2024-04-05 12:19:36 +02:00
.clang-format clang-format: add array-for-each to correct formatting issues 2024-05-28 18:56:24 +02:00
.codecov.yml
.editorconfig
.gitattributes
.gitignore .gitignore: do not ignore .\#* files 2024-06-11 19:44:54 -04:00
.gitlint gitlint: do not allow treewide as an area in commit messages 2024-04-10 09:22:24 +02:00
.mailmap
.yamllint
CMakeLists.txt llext: disable verbose for SLID generation scripts 2024-07-09 17:21:18 +02:00
CODE_OF_CONDUCT.md coc: Update Code of Conduct to latest Contributor Covenant 2023-12-21 09:38:23 +00:00
CODEOWNERS drivers: disk: remove sdmmc_sdhc.h since no longer used 2024-06-14 18:50:47 -04:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr kconfig: llvm: Set default opt level to -Oz when building with LLVM 2024-06-14 19:05:50 -04:00
LICENSE
MAINTAINERS.yml MAINTAINERS: Exclude BT classic from BT host 2024-07-18 09:29:26 -04:00
README.rst doc: README: Rework Resources section 2023-10-17 19:05:20 +03:00
SDK_VERSION SDK_VERSION: Use Zephyr SDK 0.16.8 2024-06-04 22:59:31 -04:00
VERSION release: Zephyr v3.7.99 2024-07-26 21:14:10 +02:00
version.h.in version.h.in: Do not use @template@ 2024-05-24 18:05:41 -04:00
west.yml modules: tf-m: fix git clone during build 2024-07-25 12:25:32 +02:00
zephyr-env.cmd
zephyr-env.sh

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <picture>
         <source media="(prefers-color-scheme: dark)" srcset="doc/_static/images/logo-readme-dark.svg">
         <source media="(prefers-color-scheme: light)" srcset="doc/_static/images/logo-readme-light.svg">
         <img src="doc/_static/images/logo-readme-light.svg">
       </picture>
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <a
   href="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml?query=branch%3Amain">
   <img
   src="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml/badge.svg?event=push"></a>


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM (Cortex-A,
Cortex-R, Cortex-M), Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V,
SPARC, MIPS, and a large number of `supported boards`_.

.. below included in doc/introduction/introduction.rst


Getting Started
***************

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

.. start_include_here

Community Support
*****************

Community support is provided via mailing lists and Discord; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

Getting Started
---------------

  | 📖 `Zephyr Documentation`_
  | 🚀 `Getting Started Guide`_
  | 🙋🏽 `Tips when asking for help`_
  | 💻 `Code samples`_

Code and Development
--------------------

  | 🌐 `Source Code Repository`_
  | 📦 `Releases`_
  | 🤝 `Contribution Guide`_

Community and Support
---------------------

  | 💬 `Discord Server`_ for real-time community discussions
  | 📧 `User mailing list (users@lists.zephyrproject.org)`_
  | 📧 `Developer mailing list (devel@lists.zephyrproject.org)`_
  | 📬 `Other project mailing lists`_
  | 📚 `Project Wiki`_

Issue Tracking and Security
---------------------------

  | 🐛 `GitHub Issues`_
  | 🔒 `Security documentation`_
  | 🛡️ `Security Advisories Repository`_
  | ⚠️ Report security vulnerabilities at vulnerabilities@zephyrproject.org

Additional Resources
--------------------
  | 🌐 `Zephyr Project Website`_
  | 📺 `Zephyr Tech Talks`_

.. _Zephyr Project Website: https://www.zephyrproject.org
.. _Discord Server: https://chat.zephyrproject.org
.. _supported boards: https://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: https://docs.zephyrproject.org
.. _Introduction to Zephyr: https://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: https://docs.zephyrproject.org/latest/develop/getting_started/index.html
.. _Contribution Guide: https://docs.zephyrproject.org/latest/contribute/index.html
.. _Source Code Repository: https://github.com/zephyrproject-rtos/zephyr
.. _GitHub Issues: https://github.com/zephyrproject-rtos/zephyr/issues
.. _Releases: https://github.com/zephyrproject-rtos/zephyr/releases
.. _Project Wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _User mailing list (users@lists.zephyrproject.org): https://lists.zephyrproject.org/g/users
.. _Developer mailing list (devel@lists.zephyrproject.org): https://lists.zephyrproject.org/g/devel
.. _Other project mailing lists: https://lists.zephyrproject.org/g/main/subgroups
.. _Code samples: https://docs.zephyrproject.org/latest/samples/index.html
.. _Security documentation: https://docs.zephyrproject.org/latest/security/index.html
.. _Security Advisories Repository: https://github.com/zephyrproject-rtos/zephyr/security
.. _Tips when asking for help: https://docs.zephyrproject.org/latest/develop/getting_started/index.html#asking-for-help
.. _Zephyr Tech Talks: https://www.zephyrproject.org/tech-talks