| /tests/kernel/context/ |
| A D | README.txt | 100 thread (q order: 2, t/o: 500) is running
102 thread (q order: 3, t/o: 750) is running
104 thread (q order: 0, t/o: 1000) is running
106 thread (q order: 6, t/o: 1250) is running
108 thread (q order: 1, t/o: 1500) is running
110 thread (q order: 4, t/o: 1750) is running
112 thread (q order: 5, t/o: 2000) is running
116 thread (q order: 3, t/o: 750) is running
118 thread (q order: 0, t/o: 1000) is running
122 thread (q order: 4, t/o: 1750) is running
|
| A D | Kconfig | 9 The platform may have some component running in the background while the k_cpu_idle test is
10 running causing the CPU to awake. With this option we allow for a maximum number of wakes
|
| /tests/subsys/zbus/hlp_priority_boost/ |
| A D | testcase.yaml | 8 # consumer threads running concurrently on multiple CPUs,
10 # memcpy(). So exclude these platforms from running in
|
| /tests/drivers/build_all/sensor/ |
| A D | CMakeLists.txt | 7 # Exclude main when running the generic test because ztest supplies its own
|
| A D | Kconfig | 8 Enables building and running the generic sensor test suite that will
|
| /tests/net/lib/lwm2m/lwm2m_rd_client/src/ |
| A D | stubs.c | 151 static bool running; variable
156 while (running) { in service_work_fn()
190 running = true; in test_lwm2m_engine_start_service()
202 running = false; in test_lwm2m_engine_stop_service()
|
| /tests/lib/p4workq/src/ |
| A D | main.c | 26 bool running; member
46 item->running = false; in stress_sub()
57 titem->running = true; in stress_handler()
|
| /tests/bsim/ |
| A D | sh_common.source | 58 # For a caller running from a tests_script/ folder, get the path of its parent
65 # For a caller running from a tests_script/ folder, get the path of its parent
|
| /tests/bluetooth/classic/gap_c/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/l2cap_c/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/rfcomm_c/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/sdp_s/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/smp_general/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/smp_key_persist/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/smp_sc_only/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/gap_s/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/l2cap_s/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/rfcomm_s/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/sdp_c/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/smp_bonding/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/bluetooth/classic/smp_io_cap/ |
| A D | README.rst | 10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /tests/benchmarks/sched/ |
| A D | README.rst | 20 between each numbered step and for the whole cycle, and a running
|
| /tests/drivers/can/host/ |
| A D | README.rst | 10 host PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
52 On the host PC, a virtual SocketCAN interface needs to be created and brought up before running the
113 Twister. Below is an example for running on the :zephyr:board:`lpcxpresso55s36`:
|
| /tests/subsys/debug/gdbstub/ |
| A D | testcase.yaml | 45 # with some other test on QEMU running in parallel.
|
| /tests/bsim/bluetooth/mesh/ |
| A D | README.rst | 36 When running test applications independently, make sure to assign the original
67 pattern for running a single test across N devices with different test
|