automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-test-report] |FAILURE| pw20096 [PATCH v2 2/2] mk: move PMD libraries to applications
Date: 31 Jan 2017 08:54:57 -0800	[thread overview]
Message-ID: <ffb989$142s0l@orsmga002.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2830 bytes --]

Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/20096

_apply patch file failure_

Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Tue, 31 Jan 2017 15:04:48 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:f13b12ef54e21fe166ea5fc256d80becf3f8b2db
                   Repo:dpdk-next-crypto, Branch:master, CommitID:867ee0d5aca4969558df8bb1d679a1d1bdb7c4e1
                   Repo:dpdk-next-net, Branch:master, CommitID:5b243cbab26652027c3848e35fe595025f3622ea
                   Repo:dpdk-next-virtio, Branch:master, CommitID:a69de21ee881adb095667a15a28fbf5044e22a28
                   Repo:dpdk, Branch:master, CommitID:5b243cbab26652027c3848e35fe595025f3622ea
                   
Apply patch file failed:
Repo: dpdk
20096:
patching file app/test-pmd/Makefile
Hunk #1 FAILED at 61.
Hunk #2 succeeded at 71 with fuzz 2 (offset 2 lines).
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/Makefile.rej
patching file app/test/Makefile
patching file examples/bond/Makefile
patching file mk/rte.app.mk
Hunk #1 succeeded at 100 with fuzz 1.

Repo: dpdk-next-crypto
20096:
patching file app/test-pmd/Makefile
Hunk #1 FAILED at 61.
Hunk #2 succeeded at 71 with fuzz 2 (offset 2 lines).
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/Makefile.rej
patching file app/test/Makefile
patching file examples/bond/Makefile
patching file mk/rte.app.mk
Hunk #1 succeeded at 100 with fuzz 1.

Repo: dpdk-next-net
20096:
patching file app/test-pmd/Makefile
Hunk #1 FAILED at 61.
Hunk #2 succeeded at 71 with fuzz 2 (offset 2 lines).
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/Makefile.rej
patching file app/test/Makefile
patching file examples/bond/Makefile
patching file mk/rte.app.mk
Hunk #1 succeeded at 100 with fuzz 1.

Repo: dpdk-next-virtio
20096:
patching file app/test-pmd/Makefile
Hunk #1 FAILED at 61.
Hunk #2 succeeded at 71 with fuzz 2 (offset 2 lines).
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/Makefile.rej
patching file app/test/Makefile
patching file examples/bond/Makefile
patching file mk/rte.app.mk
Hunk #1 FAILED at 100.
Hunk #2 succeeded at 133 (offset -4 lines).
Hunk #3 succeeded at 150 (offset -4 lines).
1 out of 3 hunks FAILED -- saving rejects to file mk/rte.app.mk.rej

Repo: dpdk-next-eventdev
20096:
patching file app/test-pmd/Makefile
Hunk #1 FAILED at 61.
Hunk #2 succeeded at 71 with fuzz 2 (offset 2 lines).
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/Makefile.rej
patching file app/test/Makefile
Hunk #2 succeeded at 223 (offset 2 lines).
patching file examples/bond/Makefile
patching file mk/rte.app.mk
Hunk #1 succeeded at 101 with fuzz 1 (offset 1 line).
Hunk #2 succeeded at 132 (offset 1 line).
Hunk #3 succeeded at 149 with fuzz 1 (offset 1 line).


DPDK STV team

                 reply	other threads:[~2017-01-31 16:54 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='ffb989$142s0l@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=ferruh.yigit@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).