Home
last modified time | relevance | path

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

/Zephyr-Core-2.7.6/scripts/tests/twister/
Dtest_testinstance.py29 …_run(class_testsuite, monkeypatch, all_testcases_dict, platforms_list, build_only, slow, harness, … argument
42 testcase.build_only = build_only
Dtest_testsuite_class.py98 testcase.build_only = False
/Zephyr-Core-2.7.6/scripts/
Dtwister864 suite.build_only = options.build_only
897 elif options.build_only:
1188 if options.device_testing and not options.build_only:
1285 if options.device_testing and not options.build_only:
/Zephyr-Core-2.7.6/doc/guides/test/
Dtwister.rst26 - The test is marked as ``build_only: true`` in its ``.yaml``
205 build_only: true
209 build_only: true
227 build_only: true
231 build_only: true
278 build_only: <True|False> (default False)
/Zephyr-Core-2.7.6/scripts/pylib/twister/
Dtwisterlib.py1628 self.build_only = True
1828 if self.testcase.build_only:
2623 self.build_only = False
2816 if self.platforms and not self.build_only:
2965 tc.build_only = tc_dict["build_only"]
3320 def add_tasks_to_queue(self, pipeline, build_only=False, test_only=False): argument
3322 if build_only:
3369 self.add_tasks_to_queue(pipeline, self.build_only, self.test_only)
/Zephyr-Core-2.7.6/doc/releases/
Drelease-notes-1.11.rst304 * :github:`4724` - sanitycheck build_only option can be confusing