Home
last modified time | relevance | path

Searched refs:build_only (Results 1 – 9 of 9) sorted by relevance

/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dtwister_main.py169 if options.device_testing and not options.build_only:
219 if not options.build_only:
224 if options.device_testing and not options.build_only:
Dtestinstance.py280 if self.testsuite.build_only:
Drunner.py1790 elif self.options.build_only:
1875 build_only=False, argument
1880 if build_only:
1970 self.add_tasks_to_queue(pipeline, self.options.build_only, self.options.test_only,
Dreports.py696 if self.platforms and not self.env.options.build_only:
/Zephyr-latest/scripts/tests/twister/
Dtest_testinstance.py45 build_only, argument
68 testsuite.build_only = build_only
552 testinstance.testsuite.build_only = testsuite_build_only
Dtest_runner.py2513 tr.options.build_only = None
2711 build_only, argument
2741 build_only,
2747 [build_only != instance.run for instance in instances.values()]
/Zephyr-latest/scripts/ci/coverage/
Dcoverage_analysis.py365 … testsuites,runnable,build_only,sim_only,hw_only, mixed= self._component_calculate_stats(item)
368 worksheet.write(row,col+3,build_only,cell_format)
/Zephyr-latest/doc/develop/test/
Dtwister.rst27 - The test is marked as ``build_only: true`` in its ``.yaml``
318 build_only: true
322 build_only: true
340 build_only: true
344 build_only: true
425 build_only: <True|False> (default False)
430 actually builds. A ``build_only`` test is not designed to be run in any
/Zephyr-latest/doc/releases/
Drelease-notes-1.11.rst304 * :github:`4724` - sanitycheck build_only option can be confusing