automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: george.dit@gmail.com
Subject: [dpdk-test-report] |FAILURE| pw33692 [PATCH 1/3] app/testpmd: Moved cmdline_flow to librte_cmdline
Date: 18 Jan 2018 14:44:32 -0800	[thread overview]
Message-ID: <f7a79a$qbgpe@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Georgios Katsikas <george.dit@gmail.com>
Date: Fri, 12 Jan 2018 22:01:27 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:6815f1359b0ca6c96cd9c22d1af26a4b3d794a25
                   Repo:dpdk-next-crypto, Branch:master, CommitID:8df8c445b4bea0a2fed921dc15766f33b48753d0
                   Repo:dpdk-next-net, Branch:master, CommitID:26e6baded45942b94ad9154ddd67efe8608234b4
                   Repo:dpdk-next-virtio, Branch:master, CommitID:9158926a0f24e9b8cccfe97211fa72d52a6f6a36
                   Repo:dpdk, Branch:master, CommitID:e00093f381a185e59795b554c040754b1c33c9ef
                   
Apply patch file failed:
Repo: dpdk
33692:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Hunk #2 FAILED at 77.
Hunk #3 succeeded at 752 (offset 21 lines).
Hunk #4 FAILED at 929.
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/config.c.rej
patching file app/test-pmd/testpmd.h
Hunk #3 FAILED at 129.
Hunk #4 succeeded at 677 with fuzz 1 (offset -16 lines).
1 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.h.rej
patching file lib/Makefile
patching file lib/librte_cmdline/Makefile
patching file lib/librte_cmdline/cmdline.h
patching file lib/librte_cmdline/cmdline_flow.c
patching file lib/librte_cmdline/cmdline_flow.h
patching file lib/librte_ether/rte_flow.c
Hunk #2 succeeded at 77 with fuzz 1 (offset 1 line).
Hunk #3 succeeded at 250 (offset 1 line).
Hunk #4 succeeded at 278 (offset 1 line).
patching file lib/librte_ether/rte_flow.h
Hunk #1 succeeded at 882 (offset 30 lines).
Hunk #2 succeeded at 1195 (offset 30 lines).
Hunk #3 succeeded at 1210 (offset 30 lines).

Repo: dpdk-next-crypto
33692:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Hunk #2 FAILED at 77.
Hunk #3 succeeded at 752 (offset 21 lines).
Hunk #4 FAILED at 929.
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/config.c.rej
patching file app/test-pmd/testpmd.h
Hunk #3 FAILED at 129.
Hunk #4 succeeded at 677 with fuzz 1 (offset -16 lines).
1 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.h.rej
patching file lib/Makefile
patching file lib/librte_cmdline/Makefile
patching file lib/librte_cmdline/cmdline.h
patching file lib/librte_cmdline/cmdline_flow.c
patching file lib/librte_cmdline/cmdline_flow.h
patching file lib/librte_ether/rte_flow.c
Hunk #2 succeeded at 77 with fuzz 1 (offset 1 line).
Hunk #3 succeeded at 250 (offset 1 line).
Hunk #4 succeeded at 278 (offset 1 line).
patching file lib/librte_ether/rte_flow.h
Hunk #1 succeeded at 882 (offset 30 lines).
Hunk #2 succeeded at 1195 (offset 30 lines).
Hunk #3 succeeded at 1210 (offset 30 lines).

Repo: dpdk-next-net
33692:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Hunk #2 FAILED at 77.
Hunk #3 succeeded at 752 (offset 21 lines).
Hunk #4 FAILED at 929.
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/config.c.rej
patching file app/test-pmd/testpmd.h
Hunk #3 FAILED at 129.
Hunk #4 succeeded at 677 with fuzz 1 (offset -16 lines).
1 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.h.rej
patching file lib/Makefile
patching file lib/librte_cmdline/Makefile
patching file lib/librte_cmdline/cmdline.h
patching file lib/librte_cmdline/cmdline_flow.c
patching file lib/librte_cmdline/cmdline_flow.h
patching file lib/librte_ether/rte_flow.c
Hunk #2 succeeded at 77 with fuzz 1 (offset 1 line).
Hunk #3 succeeded at 250 (offset 1 line).
Hunk #4 succeeded at 278 (offset 1 line).
patching file lib/librte_ether/rte_flow.h
Hunk #1 succeeded at 882 (offset 30 lines).
Hunk #2 succeeded at 1195 (offset 30 lines).
Hunk #3 succeeded at 1210 (offset 30 lines).

Repo: dpdk-next-virtio
33692:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Hunk #3 succeeded at 721 (offset -11 lines).
Hunk #4 FAILED at 930.
1 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/config.c.rej
patching file app/test-pmd/testpmd.h
Hunk #4 succeeded at 608 (offset -1 lines).
patching file lib/Makefile
patching file lib/librte_cmdline/Makefile
patching file lib/librte_cmdline/cmdline.h
patching file lib/librte_cmdline/cmdline_flow.c
patching file lib/librte_cmdline/cmdline_flow.h
patching file lib/librte_ether/rte_flow.c
Hunk #2 succeeded at 77 with fuzz 1 (offset 1 line).
Hunk #3 succeeded at 250 (offset 1 line).
Hunk #4 succeeded at 278 (offset 1 line).
patching file lib/librte_ether/rte_flow.h
Hunk #1 succeeded at 882 (offset 30 lines).
Hunk #2 succeeded at 1195 (offset 30 lines).
Hunk #3 succeeded at 1210 (offset 30 lines).

Repo: dpdk-next-eventdev
33692:
patching file app/test-pmd/Makefile
patching file app/test-pmd/cmdline_flow.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file app/test-pmd/cmdline_flow.c.rej
patching file app/test-pmd/config.c
Hunk #2 FAILED at 77.
Hunk #3 succeeded at 752 (offset 21 lines).
Hunk #4 FAILED at 929.
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/config.c.rej
patching file app/test-pmd/testpmd.h
Hunk #3 FAILED at 129.
Hunk #4 succeeded at 677 with fuzz 1 (offset -16 lines).
1 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.h.rej
patching file lib/Makefile
patching file lib/librte_cmdline/Makefile
patching file lib/librte_cmdline/cmdline.h
patching file lib/librte_cmdline/cmdline_flow.c
patching file lib/librte_cmdline/cmdline_flow.h
patching file lib/librte_ether/rte_flow.c
Hunk #2 succeeded at 77 with fuzz 1 (offset 1 line).
Hunk #3 succeeded at 250 (offset 1 line).
Hunk #4 succeeded at 278 (offset 1 line).
patching file lib/librte_ether/rte_flow.h
Hunk #1 succeeded at 882 (offset 30 lines).
Hunk #2 succeeded at 1195 (offset 30 lines).
Hunk #3 succeeded at 1210 (offset 30 lines).


DPDK STV team

                 reply	other threads:[~2018-01-18 22:44 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='f7a79a$qbgpe@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=george.dit@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).