|WARNING| pw140847 [PATCH v2] dts: rename execution to test run

|WARNING| pw140847 [PATCH v2] dts: rename execution to test run

[qemudev]

Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/140847

_apply patch failure_

Submitter: Juraj Linkeš <juraj.linkes@pantheon.tech>
Date: Fri,  7 Jun 2024 10:24:50 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

Apply patch set 140847 failed:

Checking patch doc/guides/tools/dts.rst...
Checking patch dts/conf.yaml...
Checking patch dts/framework/config/__init__.py...
Hunk #2 succeeded at 46 (offset -1 lines).
Hunk #3 succeeded at 428 (offset -2 lines).
Hunk #4 succeeded at 440 (offset -2 lines).
error: while searching for:
    @classmethod
    def from_dict(
        cls,
        d: ExecutionConfigDict,
        node_map: dict[str, SutNodeConfiguration | TGNodeConfiguration],
    ) -> Self:
        """A convenience method that processes the inputs before creating an instance.

error: patch failed: dts/framework/config/__init__.py:459
error: dts/framework/config/__init__.py: patch does not apply
Checking patch dts/framework/config/conf_yaml_schema.json...
Checking patch dts/framework/config/types.py...
Checking patch dts/framework/logger.py...
Checking patch dts/framework/runner.py...
error: while searching for:
        self._perf_test_case_regex = r"test_perf_"

    def run(self) -> None:
        """Run all build targets in all executions from the test run configuration.

        Before running test suites, executions and build targets are first set up.
        The executions and build targets defined in the test run configuration are iterated over.
        The executions define which tests to run and where to run them and build targets define
        the DPDK build setup.

        The tests suites are set up for each execution/build target tuple and each discovered
        test case within the test suite is set up, executed and torn down. After all test cases
        have been executed, the test suite is torn down and the next build target will be tested.

        In order to properly mark test suites and test cases as blocked in case of a failure,
        we need to have discovered which test suites and test cases to run before any failures
        happen. The discovery happens at the earliest point at the start of each execution.

        All the nested steps look like this:

            #. Execution setup

                #. Build target setup


error: patch failed: dts/framework/runner.py:95
error: dts/framework/runner.py: patch does not apply
Checking patch dts/framework/test_result.py...
Checking patch dts/framework/testbed_model/node.py...
Checking patch dts/tests/TestSuite_pmd_buffer_scatter.py...

|SUCCESS| pw140847 [PATCH v2] dts: rename execution to test run

[checkpatch]

Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/140847

_coding style OK_