automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: alejandro.lucero@netronome.com
Subject: [dpdk-test-report] |FAILURE| pw18245 [PATCH] nfp: add tso support
Date: 20 Dec 2016 03:33:17 -0800	[thread overview]
Message-ID: <9ddf0d$10qt701@fmsmga002.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: "Alejandro.Lucero" <alejandro.lucero@netronome.com>
Date: Tue, 20 Dec 2016 10:18:19 +0000
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:ee103f0ee24a8f2f2243f128796608028fc8ef4d
                   Repo:dpdk-next-net, Branch:master, CommitID:0d37eee987c981c0027ad9396e71bdbf162bae14
                   Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
                   Repo:dpdk, Branch:master, CommitID:f9de0667a609f3fdea429f0fa165a144330fd308
                   
Apply patch file failed:
Repo: dpdk-next-crypto
18245:
patching file doc/guides/nics/features/nfp.ini
Hunk #1 FAILED at 11.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/nics/features/nfp.ini.rej
patching file drivers/net/nfp/nfp_net.c
Hunk #1 FAILED at 1147.
Hunk #2 succeeded at 1519 (offset -122 lines).
Hunk #3 succeeded at 1934 (offset -96 lines).
Hunk #4 succeeded at 1983 (offset -96 lines).
Hunk #5 succeeded at 2011 (offset -96 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/nfp/nfp_net.c.rej

Repo: dpdk-next-net
18245:
patching file doc/guides/nics/features/nfp.ini
Hunk #1 succeeded at 10 (offset -1 lines).
patching file drivers/net/nfp/nfp_net.c
Hunk #1 FAILED at 1147.
Hunk #2 succeeded at 1541 (offset -100 lines).
Hunk #3 succeeded at 1924 (offset -106 lines).
Hunk #4 succeeded at 1973 (offset -106 lines).
Hunk #5 succeeded at 2001 (offset -106 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/nfp/nfp_net.c.rej

Repo: dpdk-next-virtio
18245:
patching file doc/guides/nics/features/nfp.ini
Hunk #1 FAILED at 11.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/nics/features/nfp.ini.rej
patching file drivers/net/nfp/nfp_net.c
Hunk #1 FAILED at 1147.
Hunk #2 succeeded at 1519 (offset -122 lines).
Hunk #3 succeeded at 1934 (offset -96 lines).
Hunk #4 succeeded at 1983 (offset -96 lines).
Hunk #5 succeeded at 2011 (offset -96 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/nfp/nfp_net.c.rej

Repo: dpdk
18245:
patching file doc/guides/nics/features/nfp.ini
Hunk #1 FAILED at 11.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/nics/features/nfp.ini.rej
patching file drivers/net/nfp/nfp_net.c
Hunk #1 FAILED at 1147.
Hunk #2 succeeded at 1519 (offset -122 lines).
Hunk #3 succeeded at 1934 (offset -96 lines).
Hunk #4 succeeded at 1983 (offset -96 lines).
Hunk #5 succeeded at 2011 (offset -96 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/nfp/nfp_net.c.rej


DPDK STV team

                 reply	other threads:[~2016-12-20 11:33 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='9ddf0d$10qt701@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=test-report@dpdk.org \
    /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).