automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw30194 [PATCH v2 02/18] eal: remove generic devtype
Date: 16 Oct 2017 19:20:39 -0700	[thread overview]
Message-ID: <a2ed28$14mg2ke@fmsmga002.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Thu, 12 Oct 2017 10:21:24 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c4958a2f84f03feb5a0c2b070c925bba68a87164
                   Repo:dpdk-next-crypto, Branch:master, CommitID:2f07272879a8aeae6334b4673ae1b7ffd5f35783
                   Repo:dpdk-next-net, Branch:master, CommitID:6b9ed026a8704b9e5ee5da7997617ef7cc82e114
                   Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
                   Repo:dpdk, Branch:master, CommitID:6b9ed026a8704b9e5ee5da7997617ef7cc82e114
                   
Apply patch file failed:
Repo: dpdk
30194:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
|index bbe862b..5fbcf11 100644
|--- a/drivers/bus/pci/pci_common.c
|+++ b/drivers/bus/pci/pci_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
patching file lib/librte_eal/common/eal_common_devargs.c
Hunk #1 succeeded at 153 with fuzz 1.
Hunk #2 FAILED at 165.
Hunk #3 succeeded at 206 (offset 8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_devargs.c.rej
patching file lib/librte_eal/common/eal_common_options.c
Hunk #5 FAILED at 1006.
Hunk #6 succeeded at 1130 (offset 5 lines).
1 out of 6 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_options.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/common/include/rte_devargs.h
patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map

Repo: dpdk-next-crypto
30194:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
|index bbe862b..5fbcf11 100644
|--- a/drivers/bus/pci/pci_common.c
|+++ b/drivers/bus/pci/pci_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
patching file lib/librte_eal/common/eal_common_devargs.c
Hunk #1 succeeded at 153 with fuzz 1.
Hunk #2 FAILED at 165.
Hunk #3 succeeded at 206 (offset 8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_devargs.c.rej
patching file lib/librte_eal/common/eal_common_options.c
Hunk #5 FAILED at 1006.
Hunk #6 succeeded at 1130 (offset 5 lines).
1 out of 6 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_options.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/common/include/rte_devargs.h
patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map

Repo: dpdk-next-net
30194:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
|index bbe862b..5fbcf11 100644
|--- a/drivers/bus/pci/pci_common.c
|+++ b/drivers/bus/pci/pci_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
patching file lib/librte_eal/common/eal_common_devargs.c
Hunk #1 succeeded at 153 with fuzz 1.
Hunk #2 FAILED at 165.
Hunk #3 succeeded at 206 (offset 8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_devargs.c.rej
patching file lib/librte_eal/common/eal_common_options.c
Hunk #5 FAILED at 1006.
Hunk #6 succeeded at 1130 (offset 5 lines).
1 out of 6 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_options.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/common/include/rte_devargs.h
patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map

Repo: dpdk-next-virtio
30194:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
|index bbe862b..5fbcf11 100644
|--- a/drivers/bus/pci/pci_common.c
|+++ b/drivers/bus/pci/pci_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
patching file lib/librte_eal/common/eal_common_devargs.c
Hunk #1 succeeded at 153 with fuzz 1.
Hunk #2 FAILED at 165.
Hunk #3 succeeded at 206 (offset 8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_devargs.c.rej
patching file lib/librte_eal/common/eal_common_options.c
Hunk #5 FAILED at 1006.
Hunk #6 succeeded at 1130 (offset 5 lines).
1 out of 6 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_options.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/common/include/rte_devargs.h
patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map

Repo: dpdk-next-eventdev
30194:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
|index bbe862b..5fbcf11 100644
|--- a/drivers/bus/pci/pci_common.c
|+++ b/drivers/bus/pci/pci_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
patching file lib/librte_eal/common/eal_common_devargs.c
Hunk #1 succeeded at 153 with fuzz 1.
Hunk #2 FAILED at 165.
Hunk #3 succeeded at 206 (offset 8 lines).
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_devargs.c.rej
patching file lib/librte_eal/common/eal_common_options.c
Hunk #5 FAILED at 1006.
Hunk #6 succeeded at 1130 (offset 5 lines).
1 out of 6 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_options.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/common/include/rte_devargs.h
patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map


DPDK STV team

                 reply	other threads:[~2017-10-17  2:20 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='a2ed28$14mg2ke@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=gaetan.rivet@6wind.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).