From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Luca Vizzarro <luca.vizzarro@arm.com>, zhoumin@loongson.cn
Subject: |WARNING| pw141394-141401 [PATCH v7 1/8] dts: add params manipulation module
Date: Wed, 19 Jun 2024 21:41:07 +0800 [thread overview]
Message-ID: <202406191341.45JDf7SB3733394@localhost.localdomain> (raw)
In-Reply-To: <20240619140305.293372-2-luca.vizzarro@arm.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/141394
_apply patch failure_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Wed, 19 Jun 2024 15:02:58 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e0dc4156c26bcb11c4348a079fa5fb8c4838423b
Apply patch set 141394-141401 failed:
Checking patch dts/framework/remote_session/interactive_shell.py...
error: while searching for:
from paramiko import Channel, SSHClient, channel # type: ignore[import-untyped]
from framework.logger import DTSLogger
from framework.settings import SETTINGS
error: patch failed: dts/framework/remote_session/interactive_shell.py:21
error: dts/framework/remote_session/interactive_shell.py: patch does not apply
Checking patch dts/framework/remote_session/testpmd_shell.py...
error: while searching for:
from framework.exception import InteractiveCommandExecutionError
from framework.parser import ParserFn, TextParser
from framework.settings import SETTINGS
from framework.utils import StrEnum
from .interactive_shell import InteractiveShell
error: patch failed: dts/framework/remote_session/testpmd_shell.py:28
error: dts/framework/remote_session/testpmd_shell.py: patch does not apply
Checking patch dts/framework/testbed_model/node.py...
error: while searching for:
from framework.config import OS, NodeConfiguration, TestRunConfiguration
from framework.exception import ConfigurationError
from framework.logger import DTSLogger, get_dts_logger
from framework.settings import SETTINGS
from .cpu import (
error: patch failed: dts/framework/testbed_model/node.py:19
error: dts/framework/testbed_model/node.py: patch does not apply
Checking patch dts/framework/testbed_model/os_session.py...
Hunk #3 succeeded at 136 (offset 6 lines).
Checking patch dts/framework/testbed_model/sut_node.py...
error: while searching for:
SutNodeConfiguration,
TestRunConfiguration,
)
from framework.remote_session import CommandResult
from framework.settings import SETTINGS
from framework.utils import MesonArgs
error: patch failed: dts/framework/testbed_model/sut_node.py:24
error: dts/framework/testbed_model/sut_node.py: patch does not apply
Checking patch dts/tests/TestSuite_pmd_buffer_scatter.py...
error: while searching for:
from scapy.packet import Raw # type: ignore[import-untyped]
from scapy.utils import hexstr # type: ignore[import-untyped]
from framework.remote_session.testpmd_shell import TestPmdForwardingModes, TestPmdShell
from framework.test_suite import TestSuite
error: patch failed: dts/tests/TestSuite_pmd_buffer_scatter.py:22
error: dts/tests/TestSuite_pmd_buffer_scatter.py: patch does not apply
next parent reply other threads:[~2024-06-19 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240619140305.293372-2-luca.vizzarro@arm.com>
2024-06-19 13:41 ` qemudev [this message]
2024-06-19 14:06 ` |SUCCESS| pw141394 " 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=202406191341.45JDf7SB3733394@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=luca.vizzarro@arm.com \
--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).