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| pw32866 [PATCH v3 06/15] net/avf: support stats
Date: 12 Jan 2018 10:41:02 -0800	[thread overview]
Message-ID: <a797f1$k5jcq@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Wenzhuo Lu <wenzhuo.lu@intel.com>
Date: Thu,  4 Jan 2018 13:27:04 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
                   Repo:dpdk-next-crypto, Branch:master, CommitID:8da73c32eb2cc4afc2d56a8db09a6ed30f1064c7
                   Repo:dpdk-next-net, Branch:master, CommitID:2efd988d8fe48e6a139b1295d09de215fb1a56fd
                   Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
                   Repo:dpdk, Branch:master, CommitID:f477a4696572201cf26534c83a42ec7dc8098fd8
                   
Apply patch file failed:
Repo: dpdk-next-net
32866:
patching file doc/guides/nics/features/avf.ini
Hunk #1 FAILED at 17.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/nics/features/avf.ini.rej
patching file drivers/net/avf/avf.h
Hunk #1 FAILED at 204.
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 FAILED at 40.
Hunk #2 FAILED at 56.
Hunk #3 succeeded at 1109 (offset 631 lines).
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/avf/avf_ethdev.c.rej
patching file drivers/net/avf/avf_vchnl.c
Hunk #1 succeeded at 845 with fuzz 2 (offset 152 lines).


DPDK STV team

                 reply	other threads:[~2018-01-12 18:41 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$k5jcq@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).