automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(79005) [v2] net/dpaa2: release port upon close
Date: 28 Sep 2020 19:08:46 -0700	[thread overview]
Message-ID: <fecc85$beq31v@orsmga001.jf.intel.com> (raw)

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


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

_apply issues_

Submitter: Sachin Saxena (OSS) <sachin.saxena@oss.nxp.com>
Date: 2020-09-28 10:54:28
Reply_mail: 20200928105428.14197-1-sachin.saxena@oss.nxp.com

DPDK git baseline:
	Repo:dpdk-next-net, CommitID: fc396e3ff5546c326212dea5625d7f1eb5fadd4b
	Repo:dpdk, CommitID: 77a8884c44c212d61bd3523b862dabdd30bbb00f


* Repo: dpdk-next-net
Applying: net/dpaa2: release port upon close
error: sha1 information is lacking or useless (drivers/net/dpaa2/dpaa2_ethdev.c).
error: could not build fake ancestor
Patch failed at 0001 net/dpaa2: release port upon close
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

* Repo: dpdk
exists. Then, it maps the second part, if it exists and "if mapping the
    first part succeeded".
    
    The recent change that replaces MAP_FAILED with NULL breaks the "if
    mapping the first part succeeded" condition (1) in the snippet below.
    
        void *map_addr = NULL;
--
        }
    
        if (map_addr == NULL) {
                RTE_LOG(ERR, EAL, "Failed to map pci BAR%d\n",
                        bar_index);
                return -1;
        }
--
    and the function fails. This behavior is a regression and fails
    probing hardware with vector table offset 0.
    
    Previously, (1) was "map_addr != MAP_FAILED", which meant
    pci_map_resource() was actually attempted and failed. So, expand (1)
    to check if the first part exists as well, to match the semantics of
    MAP_FAILED.
    
    Bugzilla ID: 539
    Fixes: e200535c1ca3 ("mem: drop mapping API workaround")
--
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/dpaa2/dpaa2_ethdev.c
CONFLICT (content): Merge conflict in drivers/net/dpaa2/dpaa2_ethdev.c
error: Failed to merge in the changes.
Patch failed at 0001 net/dpaa2: release port upon close
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team

                 reply	other threads:[~2020-09-29  2:08 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='fecc85$beq31v@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.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).