From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(108563) sid(22040) job(DTS_AUTO_629) [V2] test_plans/sw_hw_thash_consistence: modify test plan to adapt meson build
Date: 07 Mar 2022 17:47:25 -0800 [thread overview]
Message-ID: <722c05$g0f4ns@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/108563
Subject: [V2] test_plans/sw_hw_thash_consistence: modify test plan to adapt meson build
_Apply issues_
Diff:
test_plans/sw_hw_thash_consistence_test_plan.rst
DPDK:
commit 6eccb0c9eea51089ce14bff92697245eb342963b
Author: Haiyue Wang <haiyue.wang@intel.com>
Date: Mon Mar 7 18:25:56 2022 +0800
Comment: graph: remove useless duplicate name check
DTS:
commit fb043ef7231bcd8910fa55b072e2900d5cf2b5b5
Author: Weiyuan Li <weiyuanx.li@intel.com>
Date: Fri Feb 11 14:26:10 2022 +0800
Comment: test_plans/userspace_ethtool:remove duplicate vlan test case.
DTS git baseline:
Repo:dts, CommitID: fb043ef7231bcd8910fa55b072e2900d5cf2b5b5
* Repo: dts
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
Applying: test_plans/sw_hw_thash_consistence: modify test plan to adapt meson build
error: patch failed: test_plans/sw_hw_thash_consistence_test_plan.rst:44
error: test_plans/sw_hw_thash_consistence_test_plan.rst: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Using index info to reconstruct a base tree...
Patch failed at 0001 test_plans/sw_hw_thash_consistence: modify test plan to adapt meson build
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2022-03-08 1:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='722c05$g0f4ns@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
/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).