DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: sys_stv@intel.com
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com,
	ci@dpdk.org, john.mcnamara@intel.com, qian.q.xu@intel.com
Subject: Re: [dpdk-ci] [dpdk-test-report] |FAILURE|dpdk-master daily Intel builds
Date: Wed, 17 Jun 2020 00:18:10 +0200	[thread overview]
Message-ID: <1649592.BVoODlMcD1@thomas> (raw)
In-Reply-To: <fecc85$afifsa@orsmga001.jf.intel.com>

Hi

What is UB1804-64N?
Are you adding a new system in the CI without doing a prior full pass on it?


On an unrelated note, please it would be very helpful to have some Intel
representation in the bi-weekly CI meeting:
	http://mails.dpdk.org/archives/ci/2020-June/000655.html


16/06/2020 23:55, sys_stv@intel.com:
> Test-Label: Intel-compilation
> Test-Status: FAILURE
> _Compilation issues_
> [...]
>                  +==============================================+===========+==========+
>                  |                   Makefile                   |   Meson   | Document |
> +----------------+------+-------+------+------------+-----------+-----------+----------+
> | os             | gcc  | clang | icc  | gcc+shared | gcc+debug | gcc/clang | pdf/html |
> +----------------+------+-------+------+------------+-----------+-----------+----------+
> | UB1804-64N     | FAIL |       |      | FAIL       |           |           |          |
> | UB1804-64      | pass | pass  | pass |            |           | pass      | pass     |
> | FC32-64        | pass | pass  |      |            |           |           |          |
> | CENTOS77-64    | pass |       |      |            |           |           |          |
> | FC31-64        |      |       |      |            |           | pass      |          |
> | WIN10-64       |      |       |      |            |           | pass      |          |
> | UB2004-64      | pass | pass  | pass |            |           | pass      |          |
> | CENTOS80-64    | pass | pass  | pass | pass       | pass      | pass      |          |
> | UB1804-32      | pass |       |      |            |           | pass      |          |
> | RHEL80-64      | pass |       |      |            |           |           |          |
> | FreeBSD1201-64 | pass | pass  |      | pass       | pass      | pass      |          |
> | RHEL77-64      | pass |       |      |            |           |           |          |
> | SUSE15-64      | pass | pass  |      |            |           | pass      |          |
> +----------------+------+-------+------+------------+-----------+-----------+----------+
[...]
> *Build Build Failed #1:
> OS: UB1804-64N
> Target: x86_64-native-linuxapp-gcc
> == Build drivers/common/iavf
> In file included from <command-line>:0:0:
> ./arch/x86/include/asm/segment.h: In function ‘vdso_read_cpunode’:
> ././include/linux/compiler_types.h:210:24: error: expected ‘(’ before ‘__inline’
>  #define asm_inline asm __inline
>                         ^
> ./arch/x86/include/asm/alternative.h:240:2: note: in expansion of macro ‘asm_inline’
> --
>                  from ./include/linux/dev_printk.h:14,
>                  from ./include/linux/device.h:15,
>                  from /root/UB1804-64N_K5.4.0_GCC7.4.0/x86_64-native-linuxapp-gcc/47255110082a4530973bfa9bf0ae2870/dpdk/x86_64-native-linuxapp-gcc/build/kernel/linux/igb_uio/igb_uio.c:8:
> ./arch/x86/include/asm/alternative.h:108:2: error: expected identifier or ‘(’ before string constant
>   "# ALT: oldnstr\n"      \
>   ^
> ./arch/x86/include/asm/alternative.h:159:2: note: in expansion of macro ‘OLDINSTR’





       reply	other threads:[~2020-06-16 22:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fecc85$afifsa@orsmga001.jf.intel.com>
2020-06-16 22:18 ` Thomas Monjalon [this message]
2020-06-17 16:26   ` Aaron Conole

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=1649592.BVoODlMcD1@thomas \
    --to=thomas@monjalon.net \
    --cc=ci@dpdk.org \
    --cc=dpdk_sw_eng@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=npg.sw.core.tools.prc@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=sys_stv@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).