From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: olivier.matz@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw32034 [PATCH RFC 3/4] eal: set name when creating a control thread
Date: 08 Dec 2017 06:50:00 -0800 [thread overview]
Message-ID: <b81db2$fpth7@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4467 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32034
_apply patch file failure_
Submitter: Olivier Matz <olivier.matz@6wind.com>
Date: Fri, 8 Dec 2017 11:26:57 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c2d12ce63d4d9ea274093fe8c42fe806287fef8a
Repo:dpdk-next-crypto, Branch:master, CommitID:224374cc0e3ca44af5141fb7035a97f338d00c18
Repo:dpdk-next-net, Branch:master, CommitID:ce7eab40845ec3bd097b1071f12e3d9d6809fc0a
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:224374cc0e3ca44af5141fb7035a97f338d00c18
Apply patch file failed:
Repo: dpdk
32034:
patching file lib/librte_eal/common/eal_common_thread.c
patching file lib/librte_eal/common/include/rte_lcore.h
patching file lib/librte_eal/linuxapp/eal/eal_interrupts.c
patching file lib/librte_eal/linuxapp/eal/eal_timer.c
patching file lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
patching file lib/librte_pdump/rte_pdump.c
Hunk #1 FAILED at 577.
Hunk #2 succeeded at 584 with fuzz 1 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_pdump/rte_pdump.c.rej
patching file lib/librte_vhost/socket.c
Hunk #1 succeeded at 470 with fuzz 2.
Hunk #2 FAILED at 834.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-crypto
32034:
patching file lib/librte_eal/common/eal_common_thread.c
patching file lib/librte_eal/common/include/rte_lcore.h
patching file lib/librte_eal/linuxapp/eal/eal_interrupts.c
patching file lib/librte_eal/linuxapp/eal/eal_timer.c
patching file lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
patching file lib/librte_pdump/rte_pdump.c
Hunk #1 FAILED at 577.
Hunk #2 succeeded at 584 with fuzz 1 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_pdump/rte_pdump.c.rej
patching file lib/librte_vhost/socket.c
Hunk #1 succeeded at 470 with fuzz 2.
Hunk #2 FAILED at 834.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-net
32034:
patching file lib/librte_eal/common/eal_common_thread.c
patching file lib/librte_eal/common/include/rte_lcore.h
patching file lib/librte_eal/linuxapp/eal/eal_interrupts.c
patching file lib/librte_eal/linuxapp/eal/eal_timer.c
patching file lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
patching file lib/librte_pdump/rte_pdump.c
Hunk #1 FAILED at 577.
Hunk #2 succeeded at 584 with fuzz 1 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_pdump/rte_pdump.c.rej
patching file lib/librte_vhost/socket.c
Hunk #1 succeeded at 470 with fuzz 2.
Hunk #2 FAILED at 834.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-virtio
32034:
patching file lib/librte_eal/common/eal_common_thread.c
patching file lib/librte_eal/common/include/rte_lcore.h
patching file lib/librte_eal/linuxapp/eal/eal_interrupts.c
Hunk #1 succeeded at 875 (offset 2 lines).
Hunk #2 succeeded at 891 (offset 2 lines).
patching file lib/librte_eal/linuxapp/eal/eal_timer.c
Hunk #1 succeeded at 208 (offset 1 line).
Hunk #2 succeeded at 217 (offset 1 line).
patching file lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
patching file lib/librte_pdump/rte_pdump.c
Hunk #1 FAILED at 577.
Hunk #2 succeeded at 582 with fuzz 1 (offset -3 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_pdump/rte_pdump.c.rej
patching file lib/librte_vhost/socket.c
Hunk #1 succeeded at 469 with fuzz 2 (offset -1 lines).
Hunk #2 FAILED at 834.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-eventdev
32034:
patching file lib/librte_eal/common/eal_common_thread.c
patching file lib/librte_eal/common/include/rte_lcore.h
patching file lib/librte_eal/linuxapp/eal/eal_interrupts.c
patching file lib/librte_eal/linuxapp/eal/eal_timer.c
patching file lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
patching file lib/librte_pdump/rte_pdump.c
Hunk #1 FAILED at 577.
Hunk #2 succeeded at 584 with fuzz 1 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_pdump/rte_pdump.c.rej
patching file lib/librte_vhost/socket.c
Hunk #1 succeeded at 470 with fuzz 2.
Hunk #2 FAILED at 834.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
DPDK STV team
reply other threads:[~2017-12-08 14:50 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='b81db2$fpth7@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=olivier.matz@6wind.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).