automatic DPDK test reports
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
	"test-report@dpdk.org" <test-report@dpdk.org>
Subject: Re: [dpdk-test-report] [PatchWork]|ERROR| pw15557-15570 eal/soc: introduce very essential SoC infra definitions
Date: Fri, 2 Sep 2016 09:28:25 +0000	[thread overview]
Message-ID: <DB5PR0401MB2054400803165845165C02DE90E50@DB5PR0401MB2054.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <4f15c9$uqm8h5@fmsmga001.fm.intel.com>

These patches are failing because these are *over* the rte_driver/device patchset and not direct master. I am not sure how to convey to the test system this.
Or, is there another way to submit patches which are based over some other patch set? Or maybe I just have to ignore this.

Any comments?

-
Shreyansh

> -----Original Message-----
> From: sys_stv@intel.com [mailto:sys_stv@intel.com]
> Sent: Friday, September 02, 2016 2:47 PM
> To: Shreyansh Jain <shreyansh.jain@nxp.com>; test-report@dpdk.org
> Subject: [PatchWork]|ERROR| pw15557-15570 eal/soc: introduce very essential SoC
> infra definitions
> 
> 
> Test-Label: Intel Niantic on Fedora
> Test-Status: ERROR
> 
> Patchwork ID: 15557-15570
> http://www.dpdk.org/dev/patchwork/patch/15570/
> Submitter: Shreyansh Jain <shreyansh.jain@nxp.com>
> Date: Wed, 31 Aug 2016 16:30:22 +0530
> DPDK git baseline: e22856313fff2db12d8e132dad446bbf74cf29a5
> 
> Check patch:Success
> 
> patch file error:
> 15558:
> patching file app/test/test_soc.c
> patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
> Hunk #1 FAILED at 168.
> 1 out of 1 hunk FAILED -- saving rejects to file
> lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
> patching file lib/librte_eal/common/eal_common_soc.c
> patching file lib/librte_eal/common/include/rte_soc.h
> patching file lib/librte_eal/linuxapp/eal/Makefile
> Hunk #1 FAILED at 77.
> 1 out of 1 hunk FAILED -- saving rejects to file
> lib/librte_eal/linuxapp/eal/Makefile.rej
> patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map
> Hunk #1 FAILED at 174.
> 1 out of 1 hunk FAILED -- saving rejects to file
> lib/librte_eal/linuxapp/eal/rte_eal_version.map.rej
> 
> 15559:
> patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
> Hunk #1 FAILED at 169.
> 1 out of 1 hunk FAILED -- saving rejects to file
> lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
> patching file lib/librte_eal/common/eal_common_soc.c
> can't find file to patch at input line 99 Perhaps you used the wrong -p or --
> strip option?
> The text leading up to this was:
> --------------------------
> |diff --git a/lib/librte_eal/common/include/rte_soc.h
> |b/lib/librte_eal/common/include/rte_soc.h
> |index 16c5a1b..c6f98eb 100644
> |--- a/lib/librte_eal/common/include/rte_soc.h
> |+++ b/lib/librte_eal/common/include/rte_soc.h
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 2 out of 2 hunks ignored
> patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map
> Hunk #1 FAILED at 175.
> 1 out of 1 hunk FAILED -- saving rejects to file
> lib/librte_eal/linuxapp/eal/rte_eal_version.map.rej
> 
> 15562:
> patching file lib/librte_eal/common/eal_common_dev.c
> Hunk #1 FAILED at 106.
> Hunk #2 FAILED at 131.
> 2 out of 2 hunks FAILED -- saving rejects to file
> lib/librte_eal/common/eal_common_dev.c.rej
> patching file lib/librte_eal/common/eal_common_devargs.c
> can't find file to patch at input line 133 Perhaps you used the wrong -p or --
> strip option?
> The text leading up to this was:
> --------------------------
> |diff --git a/lib/librte_eal/common/eal_common_soc.c
> |b/lib/librte_eal/common/eal_common_soc.c
> |index 4797dd9..efa722d 100644
> |--- a/lib/librte_eal/common/eal_common_soc.c
> |+++ b/lib/librte_eal/common/eal_common_soc.c
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 5 out of 5 hunks ignored
> patching file lib/librte_eal/common/include/rte_devargs.h
> can't find file to patch at input line 264 Perhaps you used the wrong -p or --
> strip option?
> The text leading up to this was:
> --------------------------
> |diff --git a/lib/librte_eal/common/include/rte_soc.h
> |b/lib/librte_eal/common/include/rte_soc.h
> |index cc17829..c45b37e 100644
> |--- a/lib/librte_eal/common/include/rte_soc.h
> |+++ b/lib/librte_eal/common/include/rte_soc.h
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 1 out of 1 hunk ignored
> 
> 15563:
> can't find file to patch at input line 39 Perhaps you used the wrong -p or --
> strip option?
> The text leading up to this was:
> --------------------------
> |From patchwork Wed Aug 31 11:00:27 2016
> |Content-Type: text/plain; charset="utf-8"
> |MIME-Version: 1.0
> |Content-Transfer-Encoding: 7bit
> |Subject: [dpdk-dev,v2,06/14] eal/soc: implement probing of drivers
> |From: Shreyansh Jain <shreyansh.jain@nxp.com>
> |X-Patchwork-Id: 15563
> |Message-Id: <1472641235-23626-7-git-send-email-shreyansh.jain@nxp.com>
> |To: <dev@dpdk.org>
> |Cc: Shreyansh Jain <shreyansh.jain@nxp.com>, Jan Viktorin
> |<viktorin@rehivetech.com>, Hemant Agrawal <hemant.agrawal@nxp.com>
> |Date: Wed, 31 Aug 2016 16:30:27 +0530
> |
> |Each SoC PMD registers a set of callback for scanning its own bus/infra
> |and matching devices to drivers when probe is called.
> |This patch introduces the infra for calls to SoC scan on
> |rte_eal_soc_init() and match on rte_eal_soc_probe().
> |
> |Patch also adds test case for scan and probe.
> |
> |Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
> |Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> |Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> |
> |---
> |app/test/test_soc.c                             | 138 ++++++++++++++++-
> | lib/librte_eal/bsdapp/eal/rte_eal_version.map   |   3 +
> | lib/librte_eal/common/eal_common_soc.c          | 191 ++++++++++++++++++++++++
> | lib/librte_eal/common/include/rte_soc.h         |  37 +++++
> | lib/librte_eal/linuxapp/eal/eal.c               |   5 +
> | lib/librte_eal/linuxapp/eal/eal_soc.c           |  16 ++
> | lib/librte_eal/linuxapp/eal/rte_eal_version.map |   3 +
> | 7 files changed, 392 insertions(+), 1 deletion(-)
> |
> |diff --git a/app/test/test_soc.c b/app/test/test_soc.c index
> |ac03e64..4eb8146 100644
> |--- a/app/test/test_soc.c
> |+++ b/app/test/test_soc.c
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 6 out of 6 hunks ignored
> patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
> Hunk #1 FAILED at 173.
> 1 out of 1 hunk FAILED -- saving rejects to file
> lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
> can't find file to patch at input line 259 Perhaps you used the wrong -p or --
> strip option?
> The text leading up to this was:
> --------------------------
> |diff --git a/lib/librte_eal/common/eal_common_soc.c
> |b/lib/librte_eal/common/eal_common_soc.c
> |index 5dcddc5..4797dd9 100644
> |--- a/lib/librte_eal/common/eal_common_soc.c
> |+++ b/lib/librte_eal/common/eal_common_soc.c
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 3 out of 3 hunks ignored
> can't find file to patch at input line 475 Perhaps you used the wrong -p or --
> strip option?
> The text leading up to this was:
> --------------------------
> |diff --git a/lib/librte_eal/common/include/rte_soc.h
> |b/lib/librte_eal/common/include/rte_soc.h
> |index c6f98eb..cc17829 100644
> |--- a/lib/librte_eal/common/include/rte_soc.h
> |+++ b/lib/librte_eal/common/include/rte_soc.h
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 3 out of 3 hunks ignored
> patching file lib/librte_eal/linuxapp/eal/eal.c Hunk #1 FAILED at 70.
> Hunk #2 succeeded at 890 (offset 9 lines).
> 1 out of 2 hunks FAILED -- saving rejects to file
> lib/librte_eal/linuxapp/eal/eal.c.rej
> patching file lib/librte_eal/linuxapp/eal/eal_soc.c
> patching file lib/librte_eal/linuxapp/eal/rte_eal_version.map
> Hunk #1 FAILED at 179.
> 1 out of 1 hunk FAILED -- saving rejects to file
> lib/librte_eal/linuxapp/eal/rte_eal_version.map.rej
> 
> 15569:
> patching file lib/librte_ether/rte_ethdev.c Hunk #1 succeeded at 2750 (offset
> 182 lines).
> Hunk #2 FAILED at 2586.
> 1 out of 2 hunks FAILED -- saving rejects to file
> lib/librte_ether/rte_ethdev.c.rej
> 
> 15570:
> patching file lib/librte_ether/rte_ethdev.c Hunk #1 succeeded at 363 (offset 37
> lines).
> Hunk #2 succeeded at 1832 (offset 182 lines).
> Hunk #3 FAILED at 2626.
> Hunk #4 succeeded at 2839 (offset 171 lines).
> Hunk #5 succeeded at 3506 with fuzz 1 (offset 167 lines).
> 1 out of 5 hunks FAILED -- saving rejects to file
> lib/librte_ether/rte_ethdev.c.rej patching file lib/librte_ether/rte_ethdev.h
> Hunk #3 succeeded at 1632 (offset 11 lines).
> Hunk #4 succeeded at 1868 (offset 13 lines).
> Hunk #5 succeeded at 4274 (offset 26 lines).
> Hunk #6 succeeded at 4387 with fuzz 2 (offset 13 lines).
> 
> DPDK STV team

  reply	other threads:[~2016-09-02  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  9:17 sys_stv
2016-09-02  9:28 ` Shreyansh Jain [this message]
2016-09-02  9:44   ` Thomas Monjalon

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=DB5PR0401MB2054400803165845165C02DE90E50@DB5PR0401MB2054.eurprd04.prod.outlook.com \
    --to=shreyansh.jain@nxp.com \
    --cc=test-report@dpdk.org \
    --cc=thomas.monjalon@6wind.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).