From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: olivier.matz@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw23709 [PATCH 2/6] eal: move internal config initialization
Date: 19 Apr 2017 02:11:19 -0700 [thread overview]
Message-ID: <e81775$11sruq1@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2949 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23709
_apply patch file failure_
Submitter: Olivier Matz <olivier.matz@6wind.com>
Date: Tue, 18 Apr 2017 16:22:21 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:ac6183b39ad0c809055b0d32606899c7fa9dac41
Repo:dpdk-next-net, Branch:master, CommitID:b1a45a0fb5805b234753570cc760116a0e38b21c
Repo:dpdk-next-virtio, Branch:master, CommitID:bd41a0cc0bd577c6e0c67fa669bbd0d600c09bc0
Repo:dpdk, Branch:master, CommitID:4558bd902009677e3bffe5660a826e7c4e67f85d
Apply patch file failed:
Repo: dpdk
23709:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 FAILED at 323.
Hunk #2 succeeded at 519 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/eal.c.rej
patching file lib/librte_eal/linuxapp/eal/eal.c
Hunk #1 FAILED at 492.
Hunk #2 succeeded at 776 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal.c.rej
Repo: dpdk-next-crypto
23709:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 FAILED at 323.
Hunk #2 succeeded at 519 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/eal.c.rej
patching file lib/librte_eal/linuxapp/eal/eal.c
Hunk #1 FAILED at 492.
Hunk #2 succeeded at 776 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal.c.rej
Repo: dpdk-next-net
23709:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 FAILED at 323.
Hunk #2 succeeded at 519 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/eal.c.rej
patching file lib/librte_eal/linuxapp/eal/eal.c
Hunk #1 FAILED at 492.
Hunk #2 succeeded at 776 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal.c.rej
Repo: dpdk-next-virtio
23709:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 FAILED at 323.
Hunk #2 succeeded at 519 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/eal.c.rej
patching file lib/librte_eal/linuxapp/eal/eal.c
Hunk #1 FAILED at 492.
Hunk #2 succeeded at 776 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal.c.rej
Repo: dpdk-next-eventdev
23709:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 FAILED at 323.
Hunk #2 succeeded at 521 with fuzz 2 (offset 1 line).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/eal.c.rej
patching file lib/librte_eal/linuxapp/eal/eal.c
Hunk #1 FAILED at 492.
Hunk #2 succeeded at 778 with fuzz 2 (offset 1 line).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal.c.rej
DPDK STV team
reply other threads:[~2017-04-19 9:11 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$11sruq1@fmsmga001.fm.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).