automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw64162[v1] net/iavf/base: make the base code as common share
Date: 14 Jan 2020 10:30:55 -0800	[thread overview]
Message-ID: <ee68f5$932r1d@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Haiyue Wang <haiyue.wang@intel.com>
Date: 2020-01-02 05:33:38
Reply_mail: 20200102053338.112378-1-haiyue.wang@intel.com
DPDK git baseline:
	Repo:dpdk-next-net-intel, CommitID: 95edbfebfa116dffd3db7fac9a1776317acd7dd9
	Repo:dpdk, CommitID: 31bb45bcfdf5d67737eab17747b383775c9c36ae

*Repo: dpdk-next-net-intel
DIRS-y += dpaax
endif

include $(RTE_SDK)/mk/rte.subdir.mk

error: patch failed: drivers/common/Makefile:30
error: drivers/common/Makefile: patch does not apply
Checking patch drivers/common/iavf/Makefile...
error: drivers/common/iavf/Makefile: already exists in working directory
Checking patch drivers/net/iavf/base/README => drivers/common/iavf/README...
error: drivers/net/iavf/base/README: No such file or directory
--
std_deps = ['eal']
drivers = ['cpt', 'dpaax', 'mvep', 'octeontx', 'octeontx2', 'qat']
config_flag_fmt = 'RTE_LIBRTE_@0@_COMMON'
driver_name_fmt = 'rte_common_@0@'

error: patch failed: drivers/common/meson.build:2
error: drivers/common/meson.build: patch does not apply
Checking patch drivers/net/iavf/Makefile...
error: while searching for:
#
LIB = librte_pmd_iavf.a

CFLAGS += -O3 $(WERROR_FLAGS) -Wno-strict-aliasing -DALLOW_EXPERIMENTAL_API
LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
LDLIBS += -lrte_ethdev -lrte_net -lrte_kvargs -lrte_hash
LDLIBS += -lrte_bus_pci

EXPORT_MAP := rte_pmd_iavf_version.map
--

SRCS-$(CONFIG_RTE_LIBRTE_IAVF_PMD) += iavf_ethdev.c
SRCS-$(CONFIG_RTE_LIBRTE_IAVF_PMD) += iavf_vchnl.c
SRCS-$(CONFIG_RTE_LIBRTE_IAVF_PMD) += iavf_rxtx.c

error: patch failed: drivers/net/iavf/Makefile:8
error: drivers/net/iavf/Makefile: patch does not apply
Checking patch drivers/net/iavf/base/meson.build...
error: drivers/net/iavf/base/meson.build: No such file or directory
Checking patch drivers/net/iavf/iavf.h...
error: while searching for:
--
#include "base/iavf_type.h"

#define IAVF_AQ_LEN               32
#define IAVF_AQ_BUF_SZ            4096

error: patch failed: drivers/net/iavf/iavf.h:6
error: drivers/net/iavf/iavf.h: patch does not apply
Checking patch drivers/net/iavf/iavf_ethdev.c...
error: while searching for:
#include <rte_memzone.h>
#include <rte_dev.h>
--

#include "iavf.h"
#include "iavf_rxtx.h"


error: patch failed: drivers/net/iavf/iavf_ethdev.c:25
error: drivers/net/iavf/iavf_ethdev.c: patch does not apply
Checking patch drivers/net/iavf/iavf_rxtx.c...
error: while searching for:
#include <rte_ip.h>
#include <rte_net.h>
--
#include "base/iavf_type.h"
#include "iavf.h"
#include "iavf_rxtx.h"


error: patch failed: drivers/net/iavf/iavf_rxtx.c:24
error: drivers/net/iavf/iavf_rxtx.c: patch does not apply
Checking patch drivers/net/iavf/iavf_rxtx_vec_avx2.c...
error: while searching for:
 * Copyright(c) 2019 Intel Corporation
 */
--
#include "base/iavf_prototype.h"
#include "iavf_rxtx_vec_common.h"

#include <x86intrin.h>

error: patch failed: drivers/net/iavf/iavf_rxtx_vec_avx2.c:2
error: drivers/net/iavf/iavf_rxtx_vec_avx2.c: patch does not apply
Checking patch drivers/net/iavf/iavf_rxtx_vec_sse.c...
error: while searching for:
#include <rte_ethdev_driver.h>
#include <rte_malloc.h>
--
#include "base/iavf_type.h"
#include "iavf.h"
#include "iavf_rxtx.h"
#include "iavf_rxtx_vec_common.h"

error: patch failed: drivers/net/iavf/iavf_rxtx_vec_sse.c:6
error: drivers/net/iavf/iavf_rxtx_vec_sse.c: patch does not apply
Checking patch drivers/net/iavf/iavf_vchnl.c...
error: while searching for:
#include <rte_ethdev_driver.h>
#include <rte_dev.h>
--

#include "iavf.h"
#include "iavf_rxtx.h"


error: patch failed: drivers/net/iavf/iavf_vchnl.c:19
error: drivers/net/iavf/iavf_vchnl.c: patch does not apply
Checking patch drivers/net/iavf/meson.build...
error: while searching for:

allow_experimental_apis = true
--
objs = [base_objs]

sources = files(
	'iavf_ethdev.c',

error: patch failed: drivers/net/iavf/meson.build:5
error: drivers/net/iavf/meson.build: patch does not apply
Checking patch mk/rte.app.mk...
error: while searching for:
_LDLIBS-$(CONFIG_RTE_LIBRTE_I40E_PMD)       += -lrte_pmd_i40e
_LDLIBS-$(CONFIG_RTE_LIBRTE_IAVF_PMD)       += -lrte_pmd_iavf
_LDLIBS-$(CONFIG_RTE_LIBRTE_ICE_PMD)        += -lrte_pmd_ice
_LDLIBS-$(CONFIG_RTE_LIBRTE_IXGBE_PMD)      += -lrte_pmd_ixgbe
ifeq ($(CONFIG_RTE_LIBRTE_KNI),y)
_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_KNI)        += -lrte_pmd_kni

error: patch failed: mk/rte.app.mk:183
error: mk/rte.app.mk: patch does not apply
*Repo: dpdk
mem->va = NULL;

	return IAVF_SUCCESS;
}

error: patch failed: drivers/net/iavf/iavf_ethdev.c:1470
error: drivers/net/iavf/iavf_ethdev.c: patch does not apply
Checking patch drivers/net/iavf/iavf_rxtx.c...
Checking patch drivers/net/iavf/iavf_rxtx_vec_avx2.c...
Checking patch drivers/net/iavf/iavf_rxtx_vec_sse.c...
Checking patch drivers/net/iavf/iavf_vchnl.c...

DPDK STV team

                 reply	other threads:[~2020-01-14 18:31 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='ee68f5$932r1d@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).