From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hejianet@gmail.com
Subject: [dpdk-test-report] |FAILURE| pw31263 [PATCH v4 3/4] ring: introduce new header file to include common functions
Date: 08 Nov 2017 02:51:25 -0800 [thread overview]
Message-ID: <07cd09$26mv@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2889 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/31263
_apply patch file failure_
Submitter: Jia He <hejianet@gmail.com>
Date: Wed, 8 Nov 2017 09:54:40 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b96273bb75fbd99a9732aa4d49658a3525b225b0
Repo:dpdk-next-crypto, Branch:master, CommitID:c05cb4f939082fd7b4892c03372d27e870a0f426
Repo:dpdk-next-net, Branch:master, CommitID:c05cb4f939082fd7b4892c03372d27e870a0f426
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:c05cb4f939082fd7b4892c03372d27e870a0f426
Apply patch file failed:
Repo: dpdk
31263:
patching file lib/librte_eventdev/rte_event_ring.h
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
Hunk #2 succeeded at 470 (offset -5 lines).
Hunk #3 FAILED at 484.
Hunk #4 succeeded at 574 (offset -10 lines).
2 out of 4 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_generic.h
Repo: dpdk-next-crypto
31263:
patching file lib/librte_eventdev/rte_event_ring.h
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
Hunk #2 succeeded at 470 (offset -5 lines).
Hunk #3 FAILED at 484.
Hunk #4 succeeded at 574 (offset -10 lines).
2 out of 4 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_generic.h
Repo: dpdk-next-net
31263:
patching file lib/librte_eventdev/rte_event_ring.h
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
Hunk #2 succeeded at 470 (offset -5 lines).
Hunk #3 FAILED at 484.
Hunk #4 succeeded at 574 (offset -10 lines).
2 out of 4 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_generic.h
Repo: dpdk-next-virtio
31263:
patching file lib/librte_eventdev/rte_event_ring.h
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
Hunk #2 succeeded at 470 (offset -5 lines).
Hunk #3 FAILED at 484.
Hunk #4 succeeded at 574 (offset -10 lines).
2 out of 4 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_generic.h
Repo: dpdk-next-eventdev
31263:
patching file lib/librte_eventdev/rte_event_ring.h
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
Hunk #2 succeeded at 470 (offset -5 lines).
Hunk #3 FAILED at 484.
Hunk #4 succeeded at 574 (offset -10 lines).
2 out of 4 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_generic.h
DPDK STV team
reply other threads:[~2017-11-08 10:51 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='07cd09$26mv@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=hejianet@gmail.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).