From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xuemingl@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw37780 [PATCH v2 4/5] app/testpmd: introduce new tunnel VXLAN-GPE
Date: 23 Apr 2018 04:06:35 -0700 [thread overview]
Message-ID: <ca5293$1ermq7@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5132 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37780
_apply patch file failure_
Submitter: Xueming Li <xuemingl@mellanox.com>
Date: Tue, 10 Apr 2018 21:00:33 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:911137210c3af5ceea752fc4b42cc75e5f079585
Repo:dpdk-next-net, Branch:master, CommitID:e4c46085758d454f6383325f1b163942850a8697
Repo:dpdk-next-virtio, Branch:master, CommitID:ba3fec3f710a7f0289a14153500a373c4b91671d
Repo:dpdk, Branch:master, CommitID:e1d26e429a5cb0153767a5d73a0e2440b9eed2b1
Apply patch file failed:
Repo: dpdk
37780:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 succeeded at 133 (offset -4 lines).
Hunk #2 succeeded at 429 (offset -34 lines).
Hunk #3 succeeded at 552 (offset -40 lines).
Hunk #4 succeeded at 1363 (offset -87 lines).
patching file app/test-pmd/config.c
Hunk #1 succeeded at 987 (offset 15 lines).
Hunk #2 succeeded at 3034 (offset -47 lines).
patching file app/test-pmd/csumonly.c
patching file app/test-pmd/parameters.c
Hunk #2 FAILED at 186.
Hunk #3 FAILED at 621.
Hunk #4 succeeded at 1121 (offset 30 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/parameters.c.rej
patching file app/test-pmd/testpmd.h
Hunk #1 succeeded at 435 (offset -11 lines).
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 479.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej
Repo: dpdk-next-crypto
37780:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 succeeded at 133 (offset -4 lines).
Hunk #2 succeeded at 429 (offset -34 lines).
Hunk #3 succeeded at 552 (offset -40 lines).
Hunk #4 succeeded at 1363 (offset -87 lines).
patching file app/test-pmd/config.c
Hunk #1 succeeded at 987 (offset 15 lines).
Hunk #2 succeeded at 3033 (offset -48 lines).
patching file app/test-pmd/csumonly.c
patching file app/test-pmd/parameters.c
Hunk #2 FAILED at 186.
Hunk #3 FAILED at 621.
Hunk #4 succeeded at 1123 (offset 32 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/parameters.c.rej
patching file app/test-pmd/testpmd.h
Hunk #1 succeeded at 435 (offset -11 lines).
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 479.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej
Repo: dpdk-next-net
37780:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 succeeded at 133 (offset -4 lines).
Hunk #2 succeeded at 459 (offset -4 lines).
Hunk #3 succeeded at 582 (offset -10 lines).
Hunk #4 succeeded at 1404 (offset -46 lines).
patching file app/test-pmd/config.c
Hunk #1 succeeded at 987 (offset 15 lines).
Hunk #2 succeeded at 3092 (offset 11 lines).
patching file app/test-pmd/csumonly.c
patching file app/test-pmd/parameters.c
Hunk #2 FAILED at 186.
Hunk #3 FAILED at 621.
Hunk #4 succeeded at 1121 (offset 30 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/parameters.c.rej
patching file app/test-pmd/testpmd.h
Hunk #1 succeeded at 448 (offset 2 lines).
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 479.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej
Repo: dpdk-next-virtio
37780:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 succeeded at 133 (offset -4 lines).
Hunk #2 succeeded at 459 (offset -4 lines).
Hunk #3 succeeded at 582 (offset -10 lines).
Hunk #4 succeeded at 1404 (offset -46 lines).
patching file app/test-pmd/config.c
Hunk #1 succeeded at 987 (offset 15 lines).
Hunk #2 succeeded at 3091 (offset 10 lines).
patching file app/test-pmd/csumonly.c
patching file app/test-pmd/parameters.c
Hunk #2 FAILED at 186.
Hunk #3 FAILED at 621.
Hunk #4 succeeded at 1121 (offset 30 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/parameters.c.rej
patching file app/test-pmd/testpmd.h
Hunk #1 succeeded at 448 (offset 2 lines).
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 479.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej
Repo: dpdk-next-eventdev
37780:
patching file app/test-pmd/cmdline_flow.c
Hunk #1 succeeded at 133 (offset -4 lines).
Hunk #2 succeeded at 429 (offset -34 lines).
Hunk #3 succeeded at 552 (offset -40 lines).
Hunk #4 succeeded at 1363 (offset -87 lines).
patching file app/test-pmd/config.c
Hunk #1 succeeded at 971 (offset -1 lines).
Hunk #2 succeeded at 3017 (offset -64 lines).
patching file app/test-pmd/csumonly.c
patching file app/test-pmd/parameters.c
Hunk #2 FAILED at 186.
Hunk #3 FAILED at 621.
Hunk #4 succeeded at 1093 (offset 2 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/parameters.c.rej
patching file app/test-pmd/testpmd.h
Hunk #1 succeeded at 435 (offset -11 lines).
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 479.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej
DPDK STV team
reply other threads:[~2018-04-23 11:06 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='ca5293$1ermq7@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@mellanox.com \
/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).