automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: juraj.linkes@pantheon.tech, zhoumin@loongson.cn
Subject: |WARNING| pw129641-129646 [PATCH v3 1/6] dts: add scapy dependency
Date: Wed, 19 Jul 2023 22:01:24 +0800	[thread overview]
Message-ID: <202307191401.36JE1OGc358818@localhost.localdomain> (raw)
In-Reply-To: <20230719141303.33284-2-juraj.linkes@pantheon.tech>

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

_apply patch failure_

Submitter: Juraj Linkeš <juraj.linkes@pantheon.tech>
Date: Wed, 19 Jul 2023 16:12:58 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 238f67ca9cc00be4248b14d9ca4412edb7da62f6

Apply patch set 129641-129646 failed:

Checking patch dts/conf.yaml...
error: while searching for:
    skip_smoke_tests: false # optional flag that allows you to skip smoke tests
    test_suites:
      - hello_world
    system_under_test:
      node_name: "SUT 1"
      vdevs: # optional; if removed, vdevs won't be used in the execution
        - "crypto_openssl"
nodes:
  - name: "SUT 1"
    hostname: sut1.change.me.localhost

error: patch failed: dts/conf.yaml:13
error: dts/conf.yaml: patch does not apply
Checking patch dts/framework/config/__init__.py...
error: while searching for:
        return PortConfig(node=node, **d)


@dataclass(slots=True, frozen=True)
class NodeConfiguration:
    name: str

error: patch failed: dts/framework/config/__init__.py:79
error: dts/framework/config/__init__.py: patch does not apply
Checking patch dts/framework/config/conf_yaml_schema.json...
error: while searching for:
        "amount"
      ]
    },
    "pci_address": {
      "type": "string",
      "pattern": "^[\\da-fA-F]{4}:[\\da-fA-F]{2}:[\\da-fA-F]{2}.\\d:?\\w*$"

error: patch failed: dts/framework/config/conf_yaml_schema.json:164
error: dts/framework/config/conf_yaml_schema.json: patch does not apply
Checking patch dts/framework/dts.py...
Hunk #1 succeeded at 32 (offset -6 lines).
error: while searching for:
    Run the given execution. This involves running the execution setup as well as
    running all build targets in the given execution.
    """
    dts_logger.info(f"Running execution with SUT '{execution.system_under_test.name}'.")
    execution_result = result.add_execution(sut_node.config)
    execution_result.add_sut_info(sut_node.node_info)


error: patch failed: dts/framework/dts.py:87
error: dts/framework/dts.py: patch does not apply
Checking patch dts/framework/testbed_model/sut_node.py...
error: while searching for:
from framework.config import (
    BuildTargetConfiguration,
    BuildTargetInfo,
    NodeConfiguration,
    NodeInfo,
)
from framework.remote_session import CommandResult, InteractiveShellType, OSSession
from framework.settings import SETTINGS

error: patch failed: dts/framework/testbed_model/sut_node.py:12
error: dts/framework/testbed_model/sut_node.py: patch does not apply


       reply	other threads:[~2023-07-19 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230719141303.33284-2-juraj.linkes@pantheon.tech>
2023-07-19 14:01 ` qemudev [this message]
2023-07-19 14:15 ` |SUCCESS| pw129641 " checkpatch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202307191401.36JE1OGc358818@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=juraj.linkes@pantheon.tech \
    --cc=test-report@dpdk.org \
    --cc=zhoumin@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).