From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yanglong.wu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw34934 [PATCH] app/testpmd:vlan filter fail
Date: 04 Feb 2018 18:40:55 -0800 [thread overview]
Message-ID: <f7a79a$ufkha@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/34934
_apply patch file failure_
Submitter: yanglong wu <yanglong.wu@intel.com>
Date: Mon, 5 Feb 2018 01:51:38 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:ab450b9fc027b7d6aee636cf91a0bbcdc2a2f5e4
Repo:dpdk-next-crypto, Branch:master, CommitID:d98fac4dae3634fedbb6f3d568e71a30ded81dd9
Repo:dpdk-next-net, Branch:master, CommitID:d98fac4dae3634fedbb6f3d568e71a30ded81dd9
Repo:dpdk-next-virtio, Branch:master, CommitID:a1a1310df30fddaf25a6e23cff18c36969075131
Repo:dpdk, Branch:master, CommitID:d98fac4dae3634fedbb6f3d568e71a30ded81dd9
Apply patch file failed:
Repo: dpdk
34934:
patching file app/test-pmd/testpmd.c
Hunk #1 FAILED at 2324.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-crypto
34934:
patching file app/test-pmd/testpmd.c
Hunk #1 FAILED at 2324.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-net
34934:
patching file app/test-pmd/testpmd.c
Hunk #1 FAILED at 2324.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-virtio
34934:
patching file app/test-pmd/testpmd.c
Hunk #1 FAILED at 2324.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
Repo: dpdk-next-eventdev
34934:
patching file app/test-pmd/testpmd.c
Hunk #1 FAILED at 2324.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
DPDK STV team
reply other threads:[~2018-02-05 2:40 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$ufkha@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yanglong.wu@intel.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).