From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(113413) sid(23754) job(DTS_AUTO_1271) [V1] tests/multiprocess_iavf: synchronize case and testplan
Date: 24 Jun 2022 06:59:19 -0700 [thread overview]
Message-ID: <8b0460$igtgp0@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/113413
Subject: [V1] tests/multiprocess_iavf: synchronize case and testplan
_Apply issues_
Diff:
tests/TestSuite_multiprocess_iavf.py
DPDK:
commit 42fbb8e85d1f0b6c1d397d4e7559bc5877ba985e
Author: Don Wallwork <donw@xsightlabs.com>
Date: Thu Jun 23 07:21:27 2022 -0400
Comment: eal/linux: allocate worker lcore stacks in hugepages
DTS:
commit 5b1f1f829daad677af5b513b52e066b7d91e46ed
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Wed Nov 3 01:27:02 2021 +0800
Comment: version: 21.08.0
DTS git baseline:
Repo:dts, CommitID: 5b1f1f829daad677af5b513b52e066b7d91e46ed
* Repo: dts
A tests/TestSuite_multiprocess_iavf.py
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): tests/TestSuite_multiprocess_iavf.py deleted in HEAD and modified in tests/multiprocess_iavf: synchronize case and testplan. Version tests/multiprocess_iavf: synchronize case and testplan of tests/TestSuite_multiprocess_iavf.py left in tree.
error: Failed to merge in the changes.
Patch failed at 0001 tests/multiprocess_iavf: synchronize case and testplan
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-06-24 13:59 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='8b0460$igtgp0@orsmga001-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).