Searched refs:runnable (Results 1 – 10 of 10) sorted by relevance
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | reports.py | 76 runnable, argument
95 if ts_status == TwisterStatus.PASS and not runnable:
171 runnable = suite.get('runnable', 0)
183 name, classname, status, ts_status, reason, tc_duration, runnable,
245 runnable = ts.get('runnable', 0)
265 name, classname, status, ts_status, reason, tc_duration, runnable,
273 name, classname, ts_status, ts_status, reason, handler_time, runnable,
|
| D | testplan.py | 789 runnable = (self.options.device_testing or self.options.filter == 'runnable')
928 if runnable and not instance.run:
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 13 this feature. If there are two Zephyr application threads runnable on
112 illegal if called on a runnable thread. The thread must be blocked or
151 control to the appropriate runnable thread via the standard scheduler
170 until the thread that had been aborted is no longer runnable. If it
178 thread becomes runnable, the idle CPU has no way to "wake up" to
179 handle the newly-runnable load.
|
| /Zephyr-latest/scripts/ci/coverage/ |
| D | coverage_analysis.py | 365 … testsuites,runnable,build_only,sim_only,hw_only, mixed= self._component_calculate_stats(item)
367 worksheet.write(row,col+2,runnable,cell_format)
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 67 that will never see more than a small number (3, maybe) of runnable threads in
79 Use this for applications needing many concurrent runnable threads (> 20 or
97 Typical applications with small numbers of runnable threads probably want the
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 75 - The test wasn't run because it was not runnable in current configuration.
|
| D | twister.rst | 426 If true, twister will not try to run the test even if the test is runnable
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 100 Making such a thread runnable in any way thus has the effect
130 idle-but-runnable threads, and thus works only with the DUMB
315 never see more than a small number (3, maybe) of runnable
330 roughly: more than 20 or so) marked as runnable at a given
347 of threads. Typical applications with small numbers of runnable
|
| /Zephyr-latest/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | README.rst | 183 will be used and the image won't be runnable.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.7.rst | 216 * ``ZEP-865`` - convert filesystem sample to a runnable test
|
