From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ophirmu@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw35152 [PATCH v2] net/tap: fix promiscuous rules double insersions
Date: 13 Feb 2018 11:22:49 -0800 [thread overview]
Message-ID: <f7a79a$10q5s8@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7785 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/35152
_Compilation issues_
Submitter: Ophir Munk <ophirmu@mellanox.com>
Date: Tue, 13 Feb 2018 18:35:47 +0000
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:eae6e70cea2fd62a7ab2b3a6693d015e9d3d7fcc
Patch35152-35152 --> compile error
Build Summary: 15 Builds Done, 13 Successful, 2 Failures
Test environment and configuration as below:
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: 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-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
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-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
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
Failed Build #1:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-clang
In file included from /home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe.c:14:
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:377:53: error: format specifies type 'unsigned long' but the argument has type 'pthread_t' (aka 'struct pthread *') [-Werror,-Wformat]
DEBUG("Hot-plug mutex was locked by thread %lu%s", pthread_self(),
~~~ ^~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:324:32: note: expanded from macro 'DEBUG'
#define DEBUG(...) LOG_(DEBUG, __VA_ARGS__)
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:323:39: note: expanded from macro 'LOG_'
#define LOG_(level, ...) LOG__(level, __VA_ARGS__, '\n')
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:322:47: note: expanded from macro 'LOG__'
RTE_LOG(level, PMD, "net_failsafe: " m "%c", __VA_ARGS__)
^
/home/patchWorkOrg/compilation/x86_64-native-bsdapp-clang/include/rte_log.h:288:32: note: expanded from macro 'RTE_LOG'
RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
^
In file included from /home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe.c:14:
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:401:9: error: format specifies type 'unsigned long' but the argument has type 'pthread_t' (aka 'struct pthread *') [-Werror,-Wformat]
pthread_self(),
^~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:324:32: note: expanded from macro 'DEBUG'
#define DEBUG(...) LOG_(DEBUG, __VA_ARGS__)
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:323:39: note: expanded from macro 'LOG_'
#define LOG_(level, ...) LOG__(level, __VA_ARGS__, '\n')
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:322:47: note: expanded from macro 'LOG__'
RTE_LOG(level, PMD, "net_failsafe: " m "%c", __VA_ARGS__)
^
/home/patchWorkOrg/compilation/x86_64-native-bsdapp-clang/include/rte_log.h:288:32: note: expanded from macro 'RTE_LOG'
RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
^
2 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'failsafe.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'failsafe' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'net' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: 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:79: recipe for target 'install' failed
Failed Build #2:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
In file included from /home/patchWorkOrg/compilation/x86_64-native-bsdapp-gcc/include/rte_ethdev.h:150:0,
from /home/patchWorkOrg/compilation/x86_64-native-bsdapp-gcc/include/rte_ethdev_driver.h:18,
from /home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe.c:8:
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h: In function 'fs_lock':
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:236:11: error: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'pthread_t' [-Werror=format=]
((struct fs_priv *)(dev)->data->dev_private)
^
/home/patchWorkOrg/compilation/x86_64-native-bsdapp-gcc/include/rte_log.h:288:32: note: in definition of macro 'RTE_LOG'
RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:323:26: note: in expansion of macro 'LOG__'
#define LOG_(level, ...) LOG__(level, __VA_ARGS__, '\n')
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:324:20: note: in expansion of macro 'LOG_'
#define DEBUG(...) LOG_(DEBUG, __VA_ARGS__)
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:377:2: note: in expansion of macro 'DEBUG'
DEBUG("Hot-plug mutex was locked by thread %lu%s", pthread_self(),
^
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:378:8: note: in expansion of macro 'PRIV'
PRIV(dev)->alarm_lock ? " by the hot-plug alarm" : "");
^
In file included from /home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe.c:14:0:
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h: In function 'fs_unlock':
/home/patchWorkOrg/compilation/drivers/net/failsafe/failsafe_private.h:400:3: error: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'pthread_t' [-Werror=format=]
DEBUG("Hot-plug mutex was unlocked by thread %lu%s",
^
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'failsafe.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'failsafe' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'net' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: 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:79: recipe for target 'install' failed
DPDK STV team
reply other threads:[~2018-02-13 19:22 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='f7a79a$10q5s8@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=ophirmu@mellanox.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).