Go to file
Kumar Gala 34b1ef8dd8 sanitycheck: Fix process termination with newer ninja version
It appears that ninja 1.6.0 or greater don't seem to send SIGTERM down
to the child processes and thus we don't terminate correctly.  This
causes a hang with renode simulations.

Change terminate call to 'self.try_kill_process_by_pid()' when test
state is updated (i.e. done running with either passed or failed), in
order to explicitly send a SIGTERM to the simulator process before
sending a SIGTERM to ninja.

Refactor the terminate code so we encapsulate the behavior in one place
for a BinaryHandler.

Based on change from Stephanos Ioannidis <root@stephanos.io>

Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-12-12 09:17:31 -05:00
.github/ISSUE_TEMPLATE Revert "github: Add plumbing of using the github workflow labeler" 2019-11-06 19:46:32 +01:00
.known-issues
arch global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
boards doc: arm: 96b_wistrio: add EEPROM support to the boards doc 2019-12-12 07:57:33 -06:00
cmake cmake: toolchain: Don't add -Werror=implicit-int to CXX builds 2019-12-12 07:58:45 -06:00
doc doc: genrest: Use a separate index page for all symbols 2019-12-11 12:32:30 -06:00
drivers drivers: eeprom: add driver support for EEPROM of STM32L1 2019-12-12 07:57:33 -06:00
dts dts: arm: stm32: add dts support for EEPROM of STM32L1 2019-12-12 07:57:33 -06:00
ext global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
include kernel: init: provide access to kernel startup state 2019-12-11 14:45:40 -08:00
kernel kernel: init: provide access to kernel startup state 2019-12-11 14:45:40 -08:00
lib global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
misc license: cleanup: add SPDX Apache-2.0 license identifier 2019-04-07 08:45:22 -04:00
modules modules: modules: stm32 hal: Provide help section to HAL/LL symbols 2019-12-10 12:44:10 -05:00
samples global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
scripts sanitycheck: Fix process termination with newer ninja version 2019-12-12 09:17:31 -05:00
soc drivers: eeprom: add driver support for EEPROM of STM32L1 2019-12-12 07:57:33 -06:00
subsys Bluetooth: host: Refactor checks in update_ccc for efficiency 2019-12-12 15:26:38 +02:00
tests tests: eeprom: add testcase for supported boards 2019-12-12 07:57:33 -06:00
.checkpatch.conf scripts/checkpatch.pl: fix root dir detection and enable it 2019-05-22 12:40:20 -04:00
.clang-format
.codecov.yml
.editorconfig editorconfig: Set insert_final_newline true 2019-04-10 14:15:38 +02:00
.gitattributes
.gitignore docs: guide: Add build system information 2019-11-15 14:58:51 -05:00
.gitlint gitlint: match max title length restriction with checkpatch 2019-05-29 14:43:16 -04:00
.mailmap mailmap: add entry for Sean Nyekjaer 2019-11-04 14:33:31 +01:00
.shippable.yml ci: updates to fix pylint commit test 2019-09-13 10:00:16 -05:00
.uncrustify.cfg
CMakeLists.txt cmake: Zephyr module processing set modules path 2019-12-10 17:43:55 +01:00
CODE_OF_CONDUCT.md
CODEOWNERS drivers: eeprom: add driver support for EEPROM of STM32L1 2019-12-12 07:57:33 -06:00
CONTRIBUTING.rst doc: Fixed a link in CONTRIBUTING.rst 2019-02-28 12:46:04 -08:00
Kconfig kconfig: Clean up header comments and make them consistent 2019-11-04 17:31:27 -05:00
Kconfig.zephyr include: Remove compat include headers 2019-12-10 08:39:37 -05:00
LICENSE
Makefile
README.rst global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
VERSION release: post release patch level = 99 2019-12-09 21:53:34 -05:00
version.h.in cmake: explain BUILD_VERSION and KERNEL_VERSION_* 2019-05-09 11:52:05 +02:00
west.yml nrf52_bsim: Use HW models from new west module 2019-12-11 11:33:02 +01:00
zephyr-env.cmd
zephyr-env.sh zephyr_env.sh: Remove semicolons at ends of lines 2019-12-10 14:34:46 -08:00

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <img
   src="https://api.shippable.com/projects/58ffb2b8baa5e307002e1d79/badge?branch=master">


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-M,
Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
`supported boards`_.

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

.. start_include_here

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.

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

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

.. _project-resources:

Resources
*********

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

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://zephyrproject.org/developers/#downloads
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI
  (shippable) nightly build results.
* **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com.  Use
  this `Slack Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Slack Invite: https://tinyurl.com/y5glwylp
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/guides/getting-help.html