From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Nicholas Pratte <npratte@iol.unh.edu>, zhoumin@loongson.cn
Subject: |WARNING| pw153492-153497 [RFC v2 1/6] dts: rework config module to support perf TGs
Date: Sat, 17 May 2025 03:44:36 +0800 [thread overview]
Message-ID: <202505161944.54GJiaPa2962740@localhost.localdomain> (raw)
In-Reply-To: <20250516201834.626206-2-npratte@iol.unh.edu>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/153492
_apply patch failure_
Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Fri, 16 May 2025 16:18:29 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 117e86c4b96ed761e9a7ab766261208fe81bf5ca
Apply patch set 153492-153497 failed:
Checking patch dts/nodes.example.yaml => dts/configurations/nodes.example.yaml...
Checking patch dts/test_run.example.yaml => dts/configurations/test_run.example.yaml...
error: while searching for:
# in a subdirectory of DPDK tree root directory. Otherwise, will be using the `build_options`
# to build the DPDK from source. Either `precompiled_build_dir` or `build_options` can be
# defined, but not both.
traffic_generator:
type: SCAPY
perf: false # disable performance testing
func: true # enable functional testing
skip_smoke_tests: true # optional
error: patch failed: dts/test_run.example.yaml:23
error: dts/test_run.example.yaml: patch does not apply
Checking patch dts/tests_config.example.yaml => dts/configurations/tests_config.example.yaml...
Checking patch dts/configurations/trex_configs/intel_40g.yaml...
/home/zhoumin/dpdk-ci/tools/../series/35239/153492.patch:163: new blank line at EOF.
+
Checking patch dts/framework/settings.py...
next parent reply other threads:[~2025-05-16 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250516201834.626206-2-npratte@iol.unh.edu>
2025-05-16 19:44 ` qemudev [this message]
2025-05-16 20:20 ` |WARNING| pw153492 " 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=202505161944.54GJiaPa2962740@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=npratte@iol.unh.edu \
--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).