From: Ferruh Yigit <ferruh.yigit@intel.com>
To: sys_stv@intel.com, test-report@dpdk.org, thomas@monjalon.net,
Qian Xu <qian.q.xu@intel.com>
Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (53/55)
Date: Mon, 22 Oct 2018 11:46:26 +0100 [thread overview]
Message-ID: <81a6f1f1-623b-435a-93bc-44b24493fe3c@intel.com> (raw)
In-Reply-To: <f27bb3$2c2oh8@fmsmga007.fm.intel.com>
On 10/21/2018 9:30 PM, sys_stv@intel.com wrote:
> Last commit Time : Fri Oct 19 22:37:10 2018 +0200
> Last Author : Thomas Monjalon
> Last commit Hash : 739e13bcc98f562d3301f808ec76507ebae82e63
> Last comment : devargs: fix freeing during device removal
>
> Build Summary : 55 Builds Done, 53 Successful, 2 Failures.
>
> Failure details :
>
> Failure #1
> FC18_64 / Linux 3.6.10-4 / GCC 4.7.2
> Config: x86_64-native-linuxapp-gcc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y,
> CONFIG_RTE_LIBRTE_PMD_QAT=y,
> CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
> CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y
>
> DPDK/drivers/net/tap/rte_eth_tap.c: In function ‘tun_alloc’:
> DPDK/drivers/net/tap/rte_eth_tap.c:176:29: error: ‘IFF_DETACH_QUEUE’ undeclared (first use in this function)
> compilation terminated due to -Wfatal-errors.
>
> Failure #2
> FC18_64 / Linux 3.6.10-4 / ICC 16.0.2
> Config: x86_64-native-linuxapp-icc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y,
> CONFIG_RTE_LIBRTE_PMD_QAT=y,
> CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
> CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y
>
> DPDK/drivers/net/tap/rte_eth_tap.c: In function ‘tun_alloc’:
> DPDK/drivers/net/tap/rte_eth_tap.c:176:29: error: ‘IFF_DETACH_QUEUE’ undeclared (first use in this function)
> compilation terminated due to -Wfatal-errors.
This is because older kernels (< 3.8) doesn't have ‘IFF_DETACH_QUEUE’ defined.
Fedora 18 EOL on beginning of the 2014, should we still include it on our test
harness? Any objection to remove it?
And it seems Fedora coverage below is like:
FC18, FC20, FC21, FC24, FC25.
1- Why are the gaps for, intentional?
2- Why we don't have latest ones, FC27 & FC28 ?
[1]
https://en.wikipedia.org/wiki/Fedora_version_history
next prev parent reply other threads:[~2018-10-22 10:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 20:30 sys_stv
2018-10-22 10:46 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-24 20:31 sys_stv
2018-10-23 20:32 sys_stv
2018-10-22 20:31 sys_stv
2018-10-19 20:34 sys_stv
2018-10-19 7:15 sys_stv
2018-07-23 20:25 sys_stv
2018-07-22 20:39 sys_stv
2018-07-20 20:25 sys_stv
2018-07-19 20:54 sys_stv
2018-07-18 20:32 sys_stv
2018-07-13 20:29 sys_stv
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=81a6f1f1-623b-435a-93bc-44b24493fe3c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=qian.q.xu@intel.com \
--cc=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).