automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(107082) sid(21548) job(DTS_AUTO_492) [V6] test_plans/cvl_switch_filter: add test plan for cvl qinq switch filter support l4
Date: 09 Feb 2022 01:09:38 -0800	[thread overview]
Message-ID: <746b4b$g3uc8t@orsmga008-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/107082
Subject: [V6] test_plans/cvl_switch_filter: add test plan for cvl qinq switch filter support l4

_Apply issues_

Diff:
	test_plans/cvl_switch_filter_test_plan.rst

DPDK:
	commit 0dff3f26d6faad4e51f75e5245f0387ee9bb0c6d
	Author: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
	Date:   Thu Feb 3 20:13:36 2022 +0200
	Comment: eal: extend --huge-unlink for hugepage file reuse

DTS:
	commit fda10a6ad27341bb3a9d0dabe71e1484ba02903b
	Author: Yaqi Tang <yaqi.tang@intel.com>
	Date:   Mon Feb 7 23:04:05 2022 +0000
	Comment: tests/dcf_lifecycle: add test cases for CVL DCF enable device reset API

DTS git baseline:
	Repo:dts, CommitID: fda10a6ad27341bb3a9d0dabe71e1484ba02903b



* Repo: dts
Applying: test_plans/cvl_switch_filter: add test plan for cvl qinq switch filter support l4
error: corrupt patch at line 453
error: could not build fake ancestor
Patch failed at 0001 test_plans/cvl_switch_filter: add test plan for cvl qinq switch filter support l4
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-02-09  9:09 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='746b4b$g3uc8t@orsmga008-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).