automatic DPDK test reports
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: sys_stv <sys_stv@intel.com>,
	"test-report@dpdk.org" <test-report@dpdk.org>
Cc: "Xu, Qian Q" <qian.q.xu@intel.com>,
	"Van Haaren, Harry" <harry.van.haaren@intel.com>,
	"Liu, Yong" <yong.liu@intel.com>
Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (26/60)
Date: Mon, 3 Jul 2017 08:31:41 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23ED1E2DE@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <15e752$q1nj9e@FMSMGA003.fm.intel.com>

Hi,

All the compilation tests are failing because the test machine doesn't have libnuma installed.

Can someone look at that.

Thanks,

John

> -----Original Message-----
> From: test-report [mailto:test-report-bounces@dpdk.org] On Behalf Of
> sys_stv@intel.com
> Sent: Monday, July 3, 2017 9:26 AM
> To: test-report@dpdk.org
> Subject: [dpdk-test-report] | ERROR | daily Intel builds (26/60)
> 
> Last commit Time   : Sun Jul 2 19:46:52 2017 +0200
> Last Author        : Nikhil Rao
> Last commit Hash   : 5142318c8110d3bd697bf2217cfb653ebd11a0c2
> Last comment       : ethdev: fix a typo in global API introduction
> 
> Build Summary      : 60 Builds Done, 26 Successful, 34 Failures.
> 
> Failure details    :
> 
> Failure #1
> UBT144_32 / Linux 3.13.0-30 / GCC 4.8.4
> Config: i686-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
> 
> DPDK/lib/librte_eal/linuxapp/eal/eal_memory.c:58:18: fatal error: numa.h:
> No such file or directory  #include <numa.h>

  reply	other threads:[~2017-07-03  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  8:26 sys_stv
2017-07-03  8:31 ` Mcnamara, John [this message]
2017-07-03 20:14 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=B27915DBBA3421428155699D51E4CFE23ED1E2DE@IRSMSX104.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=yong.liu@intel.com \
    /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).