From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Luca Vizzarro <luca.vizzarro@arm.com>, zhoumin@loongson.cn
Subject: |WARNING| pw150105-150111 [PATCH v3 1/7] dts: enable arch self-discovery
Date: Wed, 15 Jan 2025 21:48:43 +0800 [thread overview]
Message-ID: <202501151348.50FDmhZ54072020@localhost.localdomain> (raw)
In-Reply-To: <20250115141809.3898708-2-luca.vizzarro@arm.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/150105
_apply patch failure_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Wed, 15 Jan 2025 14:18:03 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: fd51012de5369679e807be1d6a81d63ef15015ce
Apply patch set 150105-150111 failed:
Checking patch dts/conf.yaml...
Checking patch dts/framework/config/__init__.py...
Checking patch dts/framework/runner.py...
Hunk #2 succeeded at 311 (offset -4 lines).
Checking patch dts/framework/testbed_model/cpu.py...
error: while searching for:
Raises:
ValueError: If the specified lcore filter specifier is invalid.
"""
if not len(self._filter_specifier.lcore_list):
return self._lcores_to_filter
error: patch failed: dts/framework/testbed_model/cpu.py:356
error: dts/framework/testbed_model/cpu.py: patch does not apply
Checking patch dts/framework/testbed_model/linux_session.py...
Checking patch dts/framework/testbed_model/node.py...
Checking patch dts/framework/testbed_model/os_session.py...
Hunk #1 succeeded at 444 (offset -1 lines).
Checking patch dts/framework/testbed_model/sut_node.py...
Hunk #1 succeeded at 34 (offset 1 line).
Hunk #2 succeeded at 94 (offset 1 line).
Hunk #3 succeeded at 211 (offset 1 line).
next parent reply other threads:[~2025-01-15 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250115141809.3898708-2-luca.vizzarro@arm.com>
2025-01-15 13:48 ` qemudev [this message]
2025-01-15 14:20 ` |SUCCESS| pw150105 " 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=202501151348.50FDmhZ54072020@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).