From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jianfeng.tan@intel.com
Subject: [dpdk-test-report] |FAILURE| pw38556 [PATCH RFC 4/8] ipc: remove IPC thread for async request
Date: 03 May 2018 02:56:32 -0700 [thread overview]
Message-ID: <ca5293$1hkdt9@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2888 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38556
_apply patch file failure_
Submitter: Jianfeng Tan <jianfeng.tan@intel.com>
Date: Thu, 19 Apr 2018 15:03:30 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:211992f3b7df5d6d8f1dbefc48bc37a6d5398fbc
Repo:dpdk-next-net, Branch:master, CommitID:36decb6967e0563430a6e3ab0e2db3fe4ccc8db2
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:7baac775945ce26f4740158656965f095dc4dbda
Apply patch file failed:
Repo: dpdk
38556:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #3 succeeded at 301 (offset 1 line).
Hunk #4 FAILED at 453.
Hunk #5 succeeded at 627 with fuzz 1.
Hunk #6 FAILED at 672.
Hunk #7 succeeded at 856 (offset -5 lines).
Hunk #8 succeeded at 902 (offset -4 lines).
Hunk #9 succeeded at 1130 (offset -4 lines).
Hunk #10 succeeded at 1173 (offset -4 lines).
Hunk #11 succeeded at 1182 (offset -4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
Repo: dpdk-next-crypto
38556:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #3 succeeded at 301 (offset 1 line).
Hunk #4 FAILED at 453.
Hunk #5 succeeded at 627 with fuzz 1.
Hunk #6 FAILED at 672.
Hunk #7 succeeded at 856 (offset -5 lines).
Hunk #8 succeeded at 902 (offset -4 lines).
Hunk #9 succeeded at 1130 (offset -4 lines).
Hunk #10 succeeded at 1173 (offset -4 lines).
Hunk #11 succeeded at 1182 (offset -4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
Repo: dpdk-next-net
38556:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #3 succeeded at 301 (offset 1 line).
Hunk #4 FAILED at 453.
Hunk #5 succeeded at 627 with fuzz 1.
Hunk #6 FAILED at 672.
Hunk #7 succeeded at 856 (offset -5 lines).
Hunk #8 succeeded at 902 (offset -4 lines).
Hunk #9 succeeded at 1130 (offset -4 lines).
Hunk #10 succeeded at 1173 (offset -4 lines).
Hunk #11 succeeded at 1182 (offset -4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
Repo: dpdk-next-eventdev
38556:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #3 succeeded at 301 (offset 1 line).
Hunk #4 FAILED at 453.
Hunk #5 succeeded at 627 with fuzz 1.
Hunk #6 FAILED at 672.
Hunk #7 succeeded at 856 (offset -5 lines).
Hunk #8 succeeded at 902 (offset -4 lines).
Hunk #9 succeeded at 1130 (offset -4 lines).
Hunk #10 succeeded at 1173 (offset -4 lines).
Hunk #11 succeeded at 1182 (offset -4 lines).
2 out of 11 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
DPDK STV team
reply other threads:[~2018-05-03 9:56 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='ca5293$1hkdt9@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jianfeng.tan@intel.com \
--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).