Home
last modified time | relevance | path

Searched full:runnable (Results 1 – 25 of 31) sorted by relevance

12

/Zephyr-latest/scripts/ci/coverage/
Dcoverage_analysis.py84 "runnable": testsuite['runnable'],
126 "runnable": testsuite['runnable'],
163 "runnable": testsuite['runnable'],
318 if i_testsuit['runnable'] is True:
352 worksheet.write(row,col+2,"Runnable",header_format)
365 … testsuites,runnable,build_only,sim_only,hw_only, mixed= self._component_calculate_stats(item)
367 worksheet.write(row,col+2,runnable,cell_format)
477 worksheet.write(row,col+3,"Runnable",header_format)
495 if i_testsuit['runnable'] is True:
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dreports.py47 'deny_suite': ['testcases', 'execution_time', 'recording', 'retries', 'runnable']
84 runnable, argument
103 if ts_status == TwisterStatus.PASS and not runnable:
179 runnable = suite.get('runnable', 0)
191 name, classname, status, ts_status, reason, tc_duration, runnable,
253 runnable = ts.get('runnable', 0)
273 name, classname, status, ts_status, reason, tc_duration, runnable,
281 name, classname, ts_status, ts_status, reason, handler_time, runnable,
354 suite["runnable"] = False
356 suite["runnable"] = instance.run
Dtestinstance.py315 # check if test is runnable in pytest
318 filter == 'runnable' or simulator and simulator.name in SUPPORTED_SIMS_IN_PYTEST
321 if filter != 'runnable' and \
Dtestplan.py712 runnable = (self.options.device_testing or self.options.filter == 'runnable')
762 # runnable.
864 if runnable and not instance.run:
865 instance.add_filter("Not runnable on device", Filters.CMD_LINE)
Denvironment.py448 "--filter", choices=['buildable', 'runnable'],
449 default='runnable' if "--device-testing" in sys.argv else 'buildable',
451 built and if a test is runnable (emulation or a connected device), it
453 actually be run. Runnable is a subset of buildable.""")
/Zephyr-latest/soc/intel/intel_adsp/common/include/
Dsoc.h34 * may be runnable on it when this function is called (or at least the
/Zephyr-latest/scripts/tests/twister_blackbox/
Dtest_testplan.py35 ('runnable', 5),
89 ids=['buildable', 'runnable']
/Zephyr-latest/doc/kernel/services/smp/
Dsmp.rst13 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/es_upload/
Dzephyr_twister_index.json74 "runnable": { object
Dzephyr_twister_flat_recording_metrics_index.json74 "runnable": { object
Dzephyr_twister_flat_recording_index.json74 "runnable": { object
/Zephyr-latest/arch/x86/core/ia32/
Dfatal.c168 /* Restore the top half so it is runnable again */ in df_handler_bottom()
208 /* Restore the main IA task to a runnable state */ in df_handler_top()
/Zephyr-latest/drivers/timer/
Dcortex_m_systick.h56 * runnable or waiting with timeout).
/Zephyr-latest/tests/kernel/threads/thread_apis/src/
Dtest_threads_cpu_mask.c86 /* Start it. If it is runnable, it will do so in ZTEST()
/Zephyr-latest/kernel/
DKconfig97 end of the range which have "meta-irq" behavior. Runnable
101 Making such a thread runnable in any way thus has the effect
131 idle-but-runnable threads, and thus works only with the simple
323 never see more than a small number (3, maybe) of runnable
338 roughly: more than 20 or so) marked as runnable at a given
355 of threads. Typical applications with small numbers of runnable
Dsched.c53 /* Edge case: it's legal per the API to "make runnable" a in thread_runq()
55 * actually runnable!). Sort of a wart in the API and maybe in thread_runq()
885 /* A queued (runnable) old/current thread in z_get_next_switch_handle()
/Zephyr-latest/include/zephyr/drivers/mm/
Dsystem_mm.h217 * must be unmapped in the memory domains of any runnable Zephyr
260 * must be unmapped in the memory domains of any runnable Zephyr
294 * must be unmapped in the memory domains of any runnable Zephyr
/Zephyr-latest/doc/kernel/services/scheduling/
Dindex.rst69 that will never see more than a small number (3, maybe) of runnable threads in
81 Use this for applications needing many concurrent runnable threads (> 20 or
99 Typical applications with small numbers of runnable threads probably want the
/Zephyr-latest/scripts/tests/twister/
Dtest_testinstance.py516 mock.ANY, 'not runnable', mock.ANY, None, True),
519 mock.ANY, 'not runnable', [], None, True),
522 mock.ANY, 'not runnable', mock.ANY, None, False),
525 …mock.ANY, 'not runnable', ['?'], mock.Mock(duts=[mock.Mock(platform='demo_board_2', fixtures=[])])…
Dtest_testplan.py191 ("runnable", "True", "Not runnable on device"),
1358 (True, 'runnable'),
/Zephyr-latest/doc/develop/test/
Dtwister_statuses.rst75 - The test wasn't run because it was not runnable in current configuration.
/Zephyr-latest/.github/workflows/
Dcodecov.yaml108 -i --force-color -N -v --filter runnable -p ${{ matrix.platform }} --coverage \
/Zephyr-latest/tests/kernel/sched/deadline/src/
Dmain.c81 * "first" runnable thread in any given priority and in ZTEST()
/Zephyr-latest/modules/thrift/src/thrift/server/
DTServer.h122 // Allows running the server as a Runnable thread
/Zephyr-latest/tests/subsys/llext/src/
Dtest_llext.c165 /* Should be runnable from newly created thread */ in load_call_unload()

12