automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: wenzhuo.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw33347 [PATCH v6 12/14] net/avf: enable sse vector Rx Tx func
Date: 16 Jan 2018 00:03:20 -0800	[thread overview]
Message-ID: <a797f1$ljssn@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Wenzhuo Lu <wenzhuo.lu@intel.com>
Date: Wed, 10 Jan 2018 14:15:56 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
                   Repo:dpdk-next-crypto, Branch:master, CommitID:95415cfefead276dff18262c9d96df73ecb3a8de
                   Repo:dpdk-next-net, Branch:master, CommitID:fb79a5525fb9d1979654f508c197a4f6186fcaaa
                   Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
                   Repo:dpdk, Branch:master, CommitID:134975073af3a1b208e51e1fc588c53324ae2065
                   
Apply patch file failed:
Repo: dpdk-next-net
33347:
patching file config/common_base
Hunk #1 succeeded at 231 (offset 2 lines).
The next patch would create the file doc/guides/nics/features/avf_vec.ini,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/avf/Makefile
Hunk #1 FAILED at 47.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/avf/Makefile.rej
patching file drivers/net/avf/avf.h
Hunk #1 FAILED at 119.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/avf/avf.h.rej
patching file drivers/net/avf/avf_ethdev.c
Hunk #1 succeeded at 140 with fuzz 2 (offset 19 lines).
patching file drivers/net/avf/avf_rxtx.c
Hunk #1 succeeded at 141 with fuzz 1 (offset 49 lines).
Hunk #2 succeeded at 326 with fuzz 2 (offset 73 lines).
Hunk #3 FAILED at 361.
Hunk #4 succeeded at 601 with fuzz 2 (offset 228 lines).
Hunk #5 FAILED at 454.
Hunk #6 FAILED at 552.
Hunk #7 FAILED at 580.
Hunk #8 FAILED at 595.
Hunk #9 FAILED at 609.
Hunk #10 FAILED at 633.
Hunk #11 FAILED at 641.
Hunk #12 succeeded at 1724 (offset 366 lines).
Hunk #13 FAILED at 1431.
Hunk #14 succeeded at 2136 (offset 572 lines).
9 out of 14 hunks FAILED -- saving rejects to file drivers/net/avf/avf_rxtx.c.rej
patching file drivers/net/avf/avf_rxtx.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
6 out of 6 hunks ignored -- saving rejects to file drivers/net/avf/avf_rxtx.h.rej
The next patch would create the file drivers/net/avf/avf_rxtx_vec_common.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/net/avf/avf_rxtx_vec_sse.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored


DPDK STV team

                 reply	other threads:[~2018-01-16  8:03 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='a797f1$ljssn@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=wenzhuo.lu@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).