automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ajit.khaparde@broadcom.com
Subject: [dpdk-test-report] |FAILURE| pw28871 [PATCH v2 19/19] doc: update release notes
Date: 20 Sep 2017 17:30:03 -0700	[thread overview]
Message-ID: <1a8a4b$13lt9jr@fmsmga001.fm.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: FAILURE

http://dpdk.org/patch/28871

_Compilation issues_

Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Mon, 18 Sep 2017 10:17:49 -0500
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:3d2e0448ebb5c76fda6e988558793c070c3baded

Patch28853-28871 --> compile error
Build Summary: 21 Builds Done, 17 Successful, 4 Failures

Test environment and configuration as below:
OS: RHEL7.2_64
    Kernel Version:3.10.0-514.10.2.el7.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
    Clang Version:3.4.2
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-shared
OS: UB1610_64
    Kernel Version:4.8.0-22-generic
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    GCC Version:gcc (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005
    Clang Version:NA
    x86_64-native-linuxapp-icc
OS: RHEL7.3_64
    Kernel Version:3.10.0-514.16.1.el7.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11)
    Clang Version:NA
    x86_64-native-linuxapp-icc
OS: FC25_64
    Kernel Version:4.8.6-300.fc25.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    GCC Version:gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)
    Clang Version:NA
    x86_64-native-linuxapp-icc
OS: FreeBSD10.3_64
    Kernel Version:10.3-RELEASE
    CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
    GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
    Clang Version:3.4.1
    x86_64-native-bsdapp-clang
    x86_64-native-bsdapp-gcc
OS: CentOS7_64
    Kernel Version:3.10.0-514.10.2.el7.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
    Clang Version:3.4.2
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-clang
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc
OS: FC24_64
    Kernel Version:4.9.13-100.fc24.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
    Clang Version:3.8.0
    x86_64-native-linuxapp-gcc-debug
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-clang
OS: UB1604_64
    Kernel Version:4.4.0-78-generic
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
    Clang Version:3.8.0
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-clang
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc

Failed Build #1:
OS: RHEL7.2_64
Target: i686-native-linuxapp-gcc
PMDINFO bnxt_ethdev.o.pmd.c  LD bnxt_ethdev.o/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c: In function ‘bnxt_hwrm_set_ntuple_filter’:
/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c:3269:3: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t’ [-Werror=format=]
   RTE_LOG(ERR, PMD,
   ^
cc1: all warnings being treated as errors


Failed Build #2:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
PMDINFO bnxt_ethdev.o.pmd.c  LD bnxt_ethdev.o/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c: In function ‘bnxt_hwrm_set_ntuple_filter’:
/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c:3269:3: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t’ [-Werror=format=]
   RTE_LOG(ERR, PMD,
   ^
cc1: all warnings being treated as errors


Failed Build #3:
OS: FC24_64
Target: i686-native-linuxapp-gcc
PMDINFO bnxt_ethdev.o.pmd.c  LD bnxt_ethdev.oIn file included from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_debug.h:46:0,
                 from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/generic/rte_cycles.h:45,
                 from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_cycles.h:42,
                 from /home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c:38:
/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c: In function ‘bnxt_hwrm_set_ntuple_filter’:
/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c:3270:50: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t {aka long long unsigned int}’ [-Werror=format=]
    "NTUPLE id %lx\n", filter->fw_ntuple_filter_id);
                                                  ^
/home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_log.h:344:25: note: in definition of macro ‘RTE_LOG’
    RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
                         ^
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'bnxt_hwrm.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'bnxt' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'net' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:76: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:128: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:107: recipe for target 'install' failed


Failed Build #4:
OS: UB1604_64
Target: i686-native-linuxapp-gcc
PMDINFO bnxt_ethdev.o.pmd.c  LD bnxt_ethdev.oIn file included from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_debug.h:46:0,
                 from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/generic/rte_cycles.h:45,
                 from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_cycles.h:42,
                 from /home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c:38:
/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c: In function ‘bnxt_hwrm_set_ntuple_filter’:
/home/patchWorkOrg/compilation/drivers/net/bnxt/bnxt_hwrm.c:3270:50: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t {aka long long unsigned int}’ [-Werror=format=]
    "NTUPLE id %lx\n", filter->fw_ntuple_filter_id);
                                                  ^
/home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_log.h:344:25: note: in definition of macro ‘RTE_LOG’
    RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
                         ^
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'bnxt_hwrm.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'bnxt' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'net' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:76: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:128: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:107: recipe for target 'install' failed


DPDK STV team

                 reply	other threads:[~2017-09-21  0:30 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='1a8a4b$13lt9jr@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=ajit.khaparde@broadcom.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).