Home
last modified time | relevance | path

Searched +full:- +full:- +full:annotate (Results 1 – 5 of 5) sorted by relevance

/Zephyr-Core-3.4.0/.github/workflows/
Dcompliance.yml7 runs-on: ubuntu-22.04
10 - name: Update PATH for west
14 - name: Checkout the code
18 fetch-depth: 0
20 - name: cache-pip
24 key: ${{ runner.os }}-doc-pip
26 - name: Install python dependencies
30 pip3 install python-magic lxml junitparser gitlint pylint pykwalify yamllint
33 - name: west setup
37 git config --global user.email "you@example.com"
[all …]
/Zephyr-Core-3.4.0/scripts/ci/
Dcheck_compliance.py5 # SPDX-License-Identifier: Apache-2.0
46 f"{cp.stdout.decode('utf-8')}\n"
48 f"{cp.stderr.decode('utf-8')}\n")
50 return cp.stdout.decode("utf-8").rstrip()
59 return git('rev-list',
60 f'--max-count={-1 if "." in refspec else 1}', refspec).split()
63 filter_arg = (f'--diff-filter={filter}',) if filter else ()
64 paths_arg = ('--', *paths) if paths else ()
65 out = git('diff', '--name-only', *filter_arg, COMMIT_RANGE, *paths_arg)
112 - The magic string "<zephyr-base>" can be used to refer to the
[all …]
/Zephyr-Core-3.4.0/doc/develop/test/
Dztest.rst1 .. _test-framework:
23 * ``suite_name`` - The name of the suite. This name must be unique within a single binary.
24 * :c:type:`ztest_suite_predicate_t` - An optional predicate function to allow choosing when the
27 * :c:type:`ztest_suite_setup_t` - An optional setup function which returns a test fixture. This
29 * :c:type:`ztest_suite_before_t` - An optional before function which will run before every single
31 * :c:type:`ztest_suite_after_t` - An optional after function which will run after every single
33 * :c:type:`ztest_suite_teardown_t` - An optional teardown function which will run at the end of
38 .. code-block:: C
45 return ((const struct test_state*)global_state)->x == 5;
55 * :c:macro:`ZTEST` ``(suite_name, test_name)`` - Which can be used to add a test by ``test_name`` t…
[all …]
Dtwister.rst21 When using (at least) one ``-v`` option, twister's console output
26 - The test is marked as ``build_only: true`` in its ``.yaml``
28 - The test configuration has defined a ``harness`` but you don't have
30 - The target device is not connected and not available for flashing
31 - You or some higher level automation invoked twister with
32 ``--build-only``.
38 .. group-tab:: Linux
40 .. code-block:: bash
42 $ source zephyr-env.sh
45 .. group-tab:: Windows
[all …]
/Zephyr-Core-3.4.0/scripts/west_commands/runners/
Dcore.py6 # SPDX-License-Identifier: Apache-2.0
92 cmd = ['netstat', '-a', '-n', '-p', 'tcp']
96 cmd = ['ss', '-a', '-n', '-t']
100 cmd = ['netstat', '-a', '-n', '-p', 'tcp']
125 '''This helper class provides access to build-time configuration.
155 opt_value = re.compile('^(?P<option>CONFIG_[A-Za-z0-9_]+)=(?P<value>.*)$')
156 not_set = re.compile('^# (?P<option>CONFIG_[A-Za-z0-9_]+) is not set$')
166 value = value[1:-1]
210 - commands: set of supported commands; default is {'flash',
213 - dev_id: whether the runner supports device identifiers, in the form of an
[all …]