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(105983) sid(21220) job(DTS_AUTO_403) [V3] test_plans/dcf_lifecycle_test_plan: add test plan for CVL DCF enable device reset API
Date: 17 Jan 2022 21:42:14 -0800	[thread overview]
Message-ID: <8ea9f5$k0jtt9@fmsmga001-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/105983
Subject: [V3] test_plans/dcf_lifecycle_test_plan: add test plan for CVL DCF enable device reset API

_Apply issues_

Diff:
	test_plans/dcf_lifecycle_test_plan.rst

DPDK:
	commit cadb255e25d690d719d6f159e0a63f8be60650a5
	Author: Bruce Richardson <bruce.richardson@intel.com>
	Date:   Thu Dec 16 15:21:07 2021 +0000
	Comment: eal: add OS defines for C conditional checks

DTS:
	commit 889a137919cfa520fd7d52a3c42825e3d121b45d
	Author: Wei Ling <weix.ling@intel.com>
	Date:   Fri Jan 14 16:18:49 2022 +0800
	Comment: test_plans/*:modify dpdk app name

DTS git baseline:
	Repo:dts, CommitID: 889a137919cfa520fd7d52a3c42825e3d121b45d



* Repo: dts
Applying: test_plans/dcf_lifecycle_test_plan: add test plan for CVL DCF enable device reset API
error: corrupt patch at line 766
error: could not build fake ancestor
Patch failed at 0001 test_plans/dcf_lifecycle_test_plan: add test plan for CVL DCF enable device reset API
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-01-18  5:42 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='8ea9f5$k0jtt9@fmsmga001-auth.fm.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).