From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw36072 [PATCH v6 4/6] eal: lock IPC directory on init and send
Date: 15 Mar 2018 03:08:35 -0700 [thread overview]
Message-ID: <a7de25$qples@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3445 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36072
_apply patch file failure_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tue, 13 Mar 2018 17:42:38 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
Repo:dpdk-next-crypto, Branch:master, CommitID:7964ded554f3e02a62e8e9a92b9760d0de51346f
Repo:dpdk-next-net, Branch:master, CommitID:2155aa04629530689c13430c5d070c22d12721b1
Repo:dpdk-next-virtio, Branch:master, CommitID:fc33e147ae5e63a28c2b2c9bec5ad378c612ca36
Repo:dpdk, Branch:master, CommitID:09e1e8d256b0832a64af6d13bf96fcb49e1e7ded
Apply patch file failed:
Repo: dpdk
36072:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #2 FAILED at 361.
Hunk #3 FAILED at 371.
Hunk #5 succeeded at 472 (offset 1 line).
Hunk #6 succeeded at 494 with fuzz 2 (offset 1 line).
Hunk #7 succeeded at 512 with fuzz 1 (offset -3 lines).
Hunk #8 succeeded at 637 (offset -2 lines).
Hunk #9 succeeded at 673 with fuzz 2 (offset -2 lines).
Hunk #10 succeeded at 690 with fuzz 1 (offset -7 lines).
2 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
Repo: dpdk-next-crypto
36072:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #2 FAILED at 361.
Hunk #3 FAILED at 371.
Hunk #5 succeeded at 472 (offset 1 line).
Hunk #6 succeeded at 494 with fuzz 2 (offset 1 line).
Hunk #7 succeeded at 512 with fuzz 1 (offset -3 lines).
Hunk #8 succeeded at 637 (offset -2 lines).
Hunk #9 succeeded at 673 with fuzz 2 (offset -2 lines).
Hunk #10 succeeded at 690 with fuzz 1 (offset -7 lines).
2 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
Repo: dpdk-next-net
36072:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #2 FAILED at 361.
Hunk #3 FAILED at 371.
Hunk #5 succeeded at 472 (offset 1 line).
Hunk #6 succeeded at 494 with fuzz 2 (offset 1 line).
Hunk #7 succeeded at 512 with fuzz 1 (offset -3 lines).
Hunk #8 succeeded at 637 (offset -2 lines).
Hunk #9 succeeded at 673 with fuzz 2 (offset -2 lines).
Hunk #10 succeeded at 690 with fuzz 1 (offset -7 lines).
2 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
Repo: dpdk-next-virtio
36072:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #2 FAILED at 361.
Hunk #3 FAILED at 371.
Hunk #5 succeeded at 472 (offset 1 line).
Hunk #6 succeeded at 494 with fuzz 2 (offset 1 line).
Hunk #7 succeeded at 512 with fuzz 1 (offset -3 lines).
Hunk #8 succeeded at 637 (offset -2 lines).
Hunk #9 succeeded at 673 with fuzz 2 (offset -2 lines).
Hunk #10 succeeded at 690 with fuzz 1 (offset -7 lines).
2 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
Repo: dpdk-next-eventdev
36072:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #2 FAILED at 361.
Hunk #3 FAILED at 371.
Hunk #5 succeeded at 472 (offset 1 line).
Hunk #6 succeeded at 494 with fuzz 2 (offset 1 line).
Hunk #7 succeeded at 512 with fuzz 1 (offset -3 lines).
Hunk #8 succeeded at 637 (offset -2 lines).
Hunk #9 succeeded at 673 with fuzz 2 (offset -2 lines).
Hunk #10 succeeded at 690 with fuzz 1 (offset -7 lines).
2 out of 10 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
DPDK STV team
reply other threads:[~2018-03-15 10:08 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='a7de25$qples@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=anatoly.burakov@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).