From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: wei.zhao1@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25207 [PATCH v3 04/11] net/e1000: restore flex type filter
Date: 12 Jun 2017 08:27:36 -0700 [thread overview]
Message-ID: <e81775$12hp9u0@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2917 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25207
_apply patch file failure_
Submitter: zhao wei <wei.zhao1@intel.com>
Date: Fri, 9 Jun 2017 11:11:44 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:a93a816c27484017b86af9d19566218a846251f1
Repo:dpdk-next-crypto, Branch:master, CommitID:b1cac453935eb8d2f1dee8e7ab081711cfb0cf70
Repo:dpdk-next-net, Branch:master, CommitID:8c210571851a5436240a5e5a92876853a271ab94
Repo:dpdk-next-virtio, Branch:master, CommitID:101a00a4811479e7f66829e523c9138288831b39
Repo:dpdk, Branch:master, CommitID:a6793d47f328354d0a3a3984060bbfb967e4f91d
Apply patch file failed:
Repo: dpdk
25207:
patching file drivers/net/e1000/igb_ethdev.c
Hunk #3 FAILED at 1520.
Hunk #5 succeeded at 3915 (offset -2 lines).
Hunk #6 succeeded at 3969 (offset -2 lines).
Hunk #7 FAILED at 4032.
Hunk #8 FAILED at 4062.
Hunk #9 succeeded at 5601 (offset -8 lines).
Hunk #10 succeeded at 5621 (offset -8 lines).
3 out of 10 hunks FAILED -- saving rejects to file drivers/net/e1000/igb_ethdev.c.rej
Repo: dpdk-next-crypto
25207:
patching file drivers/net/e1000/igb_ethdev.c
Hunk #3 FAILED at 1520.
Hunk #5 succeeded at 3915 (offset -2 lines).
Hunk #6 succeeded at 3969 (offset -2 lines).
Hunk #7 FAILED at 4032.
Hunk #8 FAILED at 4062.
Hunk #9 succeeded at 5601 (offset -8 lines).
Hunk #10 succeeded at 5621 (offset -8 lines).
3 out of 10 hunks FAILED -- saving rejects to file drivers/net/e1000/igb_ethdev.c.rej
Repo: dpdk-next-net
25207:
patching file drivers/net/e1000/igb_ethdev.c
Hunk #1 succeeded at 809 (offset 28 lines).
Hunk #2 succeeded at 1058 (offset 43 lines).
Hunk #3 FAILED at 1520.
Hunk #4 FAILED at 1553.
Hunk #5 succeeded at 4043 with fuzz 1 (offset 119 lines).
Hunk #6 FAILED at 3978.
Hunk #7 FAILED at 4009.
Hunk #8 FAILED at 4039.
Hunk #9 succeeded at 5806 (offset 220 lines).
Hunk #10 FAILED at 5606.
6 out of 10 hunks FAILED -- saving rejects to file drivers/net/e1000/igb_ethdev.c.rej
Repo: dpdk-next-virtio
25207:
patching file drivers/net/e1000/igb_ethdev.c
Hunk #3 FAILED at 1520.
Hunk #5 succeeded at 3915 (offset -2 lines).
Hunk #6 succeeded at 3969 (offset -2 lines).
Hunk #7 FAILED at 4032.
Hunk #8 FAILED at 4062.
Hunk #9 succeeded at 5601 (offset -8 lines).
Hunk #10 succeeded at 5621 (offset -8 lines).
3 out of 10 hunks FAILED -- saving rejects to file drivers/net/e1000/igb_ethdev.c.rej
Repo: dpdk-next-eventdev
25207:
patching file drivers/net/e1000/igb_ethdev.c
Hunk #3 FAILED at 1520.
Hunk #5 succeeded at 3915 (offset -2 lines).
Hunk #6 succeeded at 3969 (offset -2 lines).
Hunk #7 FAILED at 4032.
Hunk #8 FAILED at 4062.
Hunk #9 succeeded at 5601 (offset -8 lines).
Hunk #10 succeeded at 5621 (offset -8 lines).
3 out of 10 hunks FAILED -- saving rejects to file drivers/net/e1000/igb_ethdev.c.rej
DPDK STV team
reply other threads:[~2017-06-12 15:27 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$12hp9u0@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=wei.zhao1@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).