From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com
Subject: [dpdk-test-report] |FAILURE| pw21541 [PATCH v2 11/14] ring: reduce scope of local variables
Date: 08 Mar 2017 13:23:00 -0800 [thread overview]
Message-ID: <e81775$11c98v0@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2392 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/21541
_apply patch file failure_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tue, 7 Mar 2017 11:32:14 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:720dbd63fd5083f8cacd6c59aa3f2651121d562a
Repo:dpdk-next-crypto, Branch:master, CommitID:13f57aba3e9f4f6818f525c2e402ac75d5ec7967
Repo:dpdk-next-net, Branch:master, CommitID:ce47e382ceaf2ab0515051cefbd9987c81da4ede
Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
Repo:dpdk, Branch:master, CommitID:c9051455d6bcd4bfdffdc83c8f2c329a7534921c
Apply patch file failed:
Repo: dpdk
21541:
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 288.
Hunk #2 succeeded at 380 with fuzz 2 (offset 66 lines).
Hunk #3 FAILED at 365.
Hunk #4 FAILED at 435.
Hunk #5 FAILED at 499.
Hunk #6 FAILED at 570.
5 out of 6 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-crypto
21541:
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 288.
Hunk #2 succeeded at 380 with fuzz 2 (offset 66 lines).
Hunk #3 FAILED at 365.
Hunk #4 FAILED at 435.
Hunk #5 FAILED at 499.
Hunk #6 FAILED at 570.
5 out of 6 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-net
21541:
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 288.
Hunk #2 succeeded at 380 with fuzz 2 (offset 66 lines).
Hunk #3 FAILED at 365.
Hunk #4 FAILED at 435.
Hunk #5 FAILED at 499.
Hunk #6 FAILED at 570.
5 out of 6 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-virtio
21541:
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 288.
Hunk #2 succeeded at 380 with fuzz 2 (offset 66 lines).
Hunk #3 FAILED at 365.
Hunk #4 FAILED at 435.
Hunk #5 FAILED at 499.
Hunk #6 FAILED at 570.
5 out of 6 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
Repo: dpdk-next-eventdev
21541:
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 288.
Hunk #2 succeeded at 380 with fuzz 2 (offset 66 lines).
Hunk #3 FAILED at 365.
Hunk #4 FAILED at 435.
Hunk #5 FAILED at 499.
Hunk #6 FAILED at 570.
5 out of 6 hunks FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
DPDK STV team
reply other threads:[~2017-03-08 21:23 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='e81775$11c98v0@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=bruce.richardson@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).