Searched refs:plan (Results 1 – 25 of 27) sorted by relevance
12
| /Zephyr-Core-3.7.0/scripts/tests/twister/ |
| D | conftest.py | 61 plan = TestPlan(env)
62 plan.parse_configuration(config_file=env.test_config)
63 return plan
79 plan = TestPlan(class_testplan.env)
80 plan.parse_configuration(config_file=class_testplan.env.test_config)
81 plan.add_configurations()
82 return plan.platforms
|
| D | test_testplan.py | 61 plan = TestPlan(class_env)
62 plan.parse_configuration(config_file=class_env.test_config)
64 plan.add_configurations()
65 assert sorted(plan.default_platforms) == sorted(['demo_board_1', 'demo_board_3'])
67 plan.add_configurations()
68 assert sorted(plan.default_platforms) != sorted(['demo_board_1'])
73 plan = class_testplan
74 plan.testsuites = all_testsuites_dict
89 assert sorted(plan.get_all_tests()) == sorted(expected_tests)
93 plan = class_testplan
[all …]
|
| /Zephyr-Core-3.7.0/doc/project/ |
| D | proposals.rst | 25 A request or plan to port an existing feature or enhancement to a particular
69 plan is a tactical document designed to capture and track the features planned
72 - The project roadmap communicates the why; a release plan details the what
73 - A release plan spans only a few months; a product roadmap might cover a year
84 can help the project present its plan in a compelling way to existing and new
87 they are still executing according to plan.
96 The release plan comes into play when the project roadmap's high-level strategy
97 is translated into an actionable plan built on specific features, enhancements,
100 The release plan communicates those features and enhancements slated for your
102 project plan, breaking the big ideas down into smaller projects the community
|
| D | tsc.rst | 68 Collaborate with the release manager and other stakeholders to plan and
|
| /Zephyr-Core-3.7.0/scripts/pylib/twister/twisterlib/ |
| D | reports.py | 31 def __init__(self, plan, env) -> None: argument
32 self.plan = plan #FIXME
33 self.instances = plan.instances
34 self.platforms = plan.platforms
35 self.selected_platforms = plan.selected_platforms
36 self.filtered_platforms = plan.filtered_platforms
40 self.instance_fail_count = plan.instance_fail_count
579 Fore.YELLOW if self.plan.warnings else Fore.RESET,
580 self.plan.warnings,
|
| /Zephyr-Core-3.7.0/scripts/footprint/ |
| D | track.py | 27 with open(args.plan) as csvfile:
|
| /Zephyr-Core-3.7.0/scripts/pylib/pytest-twister-harness/ |
| D | README.rst | 8 If you plan to use this plugin with Twister, then you don't need to install it
|
| /Zephyr-Core-3.7.0/doc/hardware/cache/ |
| D | index.rst | 19 set whether we plan to support and use the caches in Zephyr or not.
|
| /Zephyr-Core-3.7.0/doc/develop/test/ |
| D | twister.rst | 1382 A plan to be used verifying basic zephyr features.
1385 A plan to be used verifying unit test.
1388 A plan to be used verifying integration.
1391 A plan to be used verifying acceptance.
1394 A plan to be used verifying system.
1397 A plan to be used verifying regression.
|
| /Zephyr-Core-3.7.0/subsys/net/ip/ |
| D | Kconfig.ipv6 | 96 of memory so you need to plan this and increase the network buffer
|
| /Zephyr-Core-3.7.0/boards/nxp/s32z2xxdc2/doc/ |
| D | index.rst | 156 Follow the installation steps of the debug tool you plan to use before loading
|
| /Zephyr-Core-3.7.0/boards/acrn/acrn/doc/ |
| D | index.rst | 154 If you plan to run Zephyr with one CPU only, you can skip it.
|
| /Zephyr-Core-3.7.0/doc/contribute/ |
| D | external.rst | 117 migration plan.
|
| /Zephyr-Core-3.7.0/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 50 Note that if you plan to use SOF on your board, you will need to build and
|
| D | chromebooks_adsp.rst | 55 plan on a strategy that can tolerate data loss on the device you're
|
| /Zephyr-Core-3.7.0/doc/safety/ |
| D | safety_overview.rst | 69 includes the identification of safety requirements, the development of a safety plan, and the
|
| /Zephyr-Core-3.7.0/scripts/ |
| D | spelling.txt | 1136 paln||plan
|
| /Zephyr-Core-3.7.0/doc/releases/ |
| D | release-notes-2.2.rst | 1229 …thub:`6562` - Question: Is QP™ Real-Time Frameworks/RTOS or libev supported in Zephyr? Or any plan?
1231 * :github:`6496` - Question: Is dynamical module loader supported in Zephyr? Or any plan?
|
| D | release-notes-2.0.rst | 1451 * :github:`6817` - Question: Is supported for stack sharing among tasks in Zephyr? Or any plan?
1452 * :github:`6816` - Question: Is KProbes supported in Zephyr? Or any plan?
|
| D | release-notes-1.12.rst | 455 * :github:`6657` - Question: Is Bluetooth avrcp supported in Zephyr? Or any plan?
|
| D | release-notes-2.5.rst | 1336 * :github:`30178` - Is there any plan to support NXP RT600 HIFI4 DSP in the zephyr project?
1953 * :github:`6818` - Question: Is Lightweight OpenMP implementation supported in Zephyr? Or any plan?
|
| D | release-notes-2.7.rst | 1971 * :github:`6657` - Question: Is Bluetooth avrcp supported in Zephyr? Or any plan?
|
| /Zephyr-Core-3.7.0/doc/security/ |
| D | security-overview.rst | 605 hardware platform), a suitable VA plan shall be created and executed.
|
| /Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/audio/ |
| D | bluetooth-le-audio-arch.rst | 1248 discuss and plan the development of LE Audio in Zephyr. You can find the time of the meetings by
|
| /Zephyr-Core-3.7.0/doc/contribute/coding_guidelines/ |
| D | index.rst | 166 …ei.cmu.edu/confluence/display/c/STR01-C.+Adopt+and+implement+a+consistent+plan+for+managing+string…
|
12
