From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: arybchenko@solarflare.com
Subject: [dpdk-test-report] |FAILURE| pw38961 [PATCH v3 2/6] mempool: implement abstract mempool info API
Date: 08 May 2018 08:48:17 -0700 [thread overview]
Message-ID: <0590c7$1jlu3g@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4921 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38961
_apply patch file failure_
Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Wed, 25 Apr 2018 17:32:20 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:9e3a32fcd3d10866fcd2519be3d577e557a6719c
Repo:dpdk-next-net, Branch:master, CommitID:9e1d6be043b55ac34a57d4a6ef1c16da84688f40
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:5751ff40fed0f7dc359e983d80c768126328561f
Apply patch file failed:
Repo: dpdk
38961:
patching file lib/librte_mempool/rte_mempool.h
Hunk #1 succeeded at 193 with fuzz 2 (offset 4 lines).
Hunk #2 succeeded at 593 with fuzz 2 (offset 77 lines).
Hunk #3 FAILED at 544.
Hunk #4 succeeded at 787 with fuzz 2 (offset 81 lines).
1 out of 4 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool.h.rej
patching file lib/librte_mempool/rte_mempool_ops.c
Hunk #1 FAILED at 59.
Hunk #2 succeeded at 150 with fuzz 2 (offset 16 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool_ops.c.rej
patching file lib/librte_mempool/rte_mempool_version.map
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file lib/librte_mempool/rte_mempool_version.map.rej
Repo: dpdk-next-crypto
38961:
patching file lib/librte_mempool/rte_mempool.h
Hunk #1 succeeded at 193 with fuzz 2 (offset 4 lines).
Hunk #2 succeeded at 593 with fuzz 2 (offset 77 lines).
Hunk #3 FAILED at 544.
Hunk #4 succeeded at 787 with fuzz 2 (offset 81 lines).
1 out of 4 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool.h.rej
patching file lib/librte_mempool/rte_mempool_ops.c
Hunk #1 FAILED at 59.
Hunk #2 succeeded at 150 with fuzz 2 (offset 16 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool_ops.c.rej
patching file lib/librte_mempool/rte_mempool_version.map
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file lib/librte_mempool/rte_mempool_version.map.rej
Repo: dpdk-next-net
38961:
patching file lib/librte_mempool/rte_mempool.h
Hunk #1 succeeded at 193 with fuzz 2 (offset 4 lines).
Hunk #2 succeeded at 593 with fuzz 2 (offset 77 lines).
Hunk #3 FAILED at 544.
Hunk #4 succeeded at 787 with fuzz 2 (offset 81 lines).
1 out of 4 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool.h.rej
patching file lib/librte_mempool/rte_mempool_ops.c
Hunk #1 FAILED at 59.
Hunk #2 succeeded at 150 with fuzz 2 (offset 16 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool_ops.c.rej
patching file lib/librte_mempool/rte_mempool_version.map
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file lib/librte_mempool/rte_mempool_version.map.rej
Repo: dpdk-next-virtio
38961:
patching file lib/librte_mempool/rte_mempool.h
Hunk #1 succeeded at 193 with fuzz 2 (offset 4 lines).
Hunk #2 succeeded at 593 with fuzz 2 (offset 77 lines).
Hunk #3 FAILED at 544.
Hunk #4 succeeded at 787 with fuzz 2 (offset 81 lines).
1 out of 4 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool.h.rej
patching file lib/librte_mempool/rte_mempool_ops.c
Hunk #1 FAILED at 59.
Hunk #2 succeeded at 150 with fuzz 2 (offset 16 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool_ops.c.rej
patching file lib/librte_mempool/rte_mempool_version.map
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file lib/librte_mempool/rte_mempool_version.map.rej
Repo: dpdk-next-eventdev
38961:
patching file lib/librte_mempool/rte_mempool.h
Hunk #1 succeeded at 193 with fuzz 2 (offset 4 lines).
Hunk #2 succeeded at 593 with fuzz 2 (offset 77 lines).
Hunk #3 FAILED at 544.
Hunk #4 succeeded at 787 with fuzz 2 (offset 81 lines).
1 out of 4 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool.h.rej
patching file lib/librte_mempool/rte_mempool_ops.c
Hunk #1 FAILED at 59.
Hunk #2 succeeded at 150 with fuzz 2 (offset 16 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_mempool/rte_mempool_ops.c.rej
patching file lib/librte_mempool/rte_mempool_version.map
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file lib/librte_mempool/rte_mempool_version.map.rej
DPDK STV team
reply other threads:[~2018-05-08 15:48 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='0590c7$1jlu3g@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=arybchenko@solarflare.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).