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(108336) sid(21882) job(DTS_AUTO_570) [V4] framework/*: Modified create_eal_parameters API to support flexibility
Date: 01 Mar 2022 22:12:48 -0800	[thread overview]
Message-ID: <5975f8$f76q7r@orsmga006-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/108336
Subject: [V4] framework/*: Modified create_eal_parameters API to support flexibility

_Apply issues_

Diff:
	framework/pmd_output.py
	framework/exception.py
	framework/dut.py

DPDK:
	commit 305769000c40a4fdf1ed0cf24c157b447b91ea7d
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Sun Feb 27 21:52:48 2022 +0100
	Comment: version: 22.03-rc2

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
Falling back to patching base and 3-way merge...
Auto-merging framework/dut.py
CONFLICT (content): Merge conflict in framework/dut.py
error: Failed to merge in the changes.
Patch failed at 0001 framework/*: Modified create_eal_parameters API to support flexibility
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-02  6:12 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='5975f8$f76q7r@orsmga006-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).