automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, thomas@monjalon.net
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com
Subject: [dpdk-test-report] |FAILURE| dpdk daily Intel builds
Date: 29 Jun 2021 08:39:38 -0700	[thread overview]
Message-ID: <970444$cg6abe@fmsmga007-auth.fm.intel.com> (raw)

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


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


commit 568d97c09ca00e52fd7805ef0cab522250dac18b
Author: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date:   Sat Jun 19 16:56:28 2021 +0300

    common/mlx5: fix Netlink port name padding in probing

DPDK git Repo: dpdk 


Meson Build Summary: 25 Builds Done, 19 Successful, 6 Failures, 0 Blocked

+----------------+------------+--------------+------------+------------+-----------+----------+
| os             | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+----------------+------------+--------------+------------+------------+-----------+----------+
| UB2004-64      | pass       | pass         | pass       |            |           | pass     |
| RHEL83-64      | fail       | fail         | fail       | fail       | fail      |          |
| FC34-64        | pass       | pass         |            |            |           |          |
| UB2104-64      | pass       |              |            |            |           |          |
| WIN10-64       |            | pass         |            |            |           |          |
| UB2004-32      | pass       |              | fail       |            |           |          |
| CENTOS83-64    | pass       | pass         |            |            |           |          |
| FreeBSD1201-64 | pass       | pass         |            | pass       | pass      |          |
| SUSE15-64      | pass       | pass         |            |            |           |          |
| UB2004-64N     | pass       |              |            | pass       |           |          |
+----------------+------------+--------------+------------+------------+-----------+----------+
Test environment and configuration as below:


OS: UB2004-64
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.2.0-5ubuntu1~20.04) 10.2.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-doc

OS: RHEL83-64
	Kernel Version: 4.18.0-240.el8.x86_64
	GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
	Clang Version: 10.0.1 (Red Hat 10.0.1-1.module+el8.3.0+7459+90c24896)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug
	x86_64-native-linuxapp-icc

OS: FC34-64
	Kernel Version: 5.11.15-300.fc34.x86_64
	GCC Version: gcc (GCC) 11.0.1 20210324 (Red Hat 11.0.1-0)
	Clang Version: 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: UB2104-64
	Kernel Version: 5.11.0-16-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0
	Clang Version: 12.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc

OS: WIN10-64
	Kernel Version: N/A
	GCC Version: N/A
	Clang Version: Clang 8.0.0
	x86_64-windows-clang

OS: UB2004-32
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.2.0-5ubuntu1~20.04) 10.2.0
	Clang Version: 10.0.0-4ubuntu1
	i686-native-linuxapp-gcc
	i686-native-linuxapp-icc

OS: CENTOS83-64
	Kernel Version: 4.18.0-240.1.1.el8_3.x86_64
	GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
	Clang Version: 10.0.1 (Red Hat 10.0.1-1.module_el8.3.0+467+cb298d5b)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: FreeBSD1201-64
	Kernel Version: 12.1-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 9.2.0
	Clang Version: 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc+debug

OS: SUSE15-64
	Kernel Version: 5.3.18-lp152.57-default
	GCC Version: gcc (SUSE Linux) 7.5.0
	Clang Version: 9.0.1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc

OS: UB2004-64N
	Kernel Version: 5.11.0-051100-generic
	GCC Version: gcc (GCC) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc+shared



*Build Failed #1:
OS: RHEL83-64
Target: x86_64-native-linuxapp-gcc
Program binutils-avx512-check.sh found: YES (/root/RHEL83-64_K4.18.0_GCC8.3.1/x86_64-native-linuxapp-gcc/4491e11f4233453a8ab6a429d9afbd2d/dpdk/buildtools/binutils-avx512-check.sh)
Program python3 found: YES (/usr/bin/python3)

buildtools/meson.build:45:8: ERROR: Problem encountered: missing python module: elftools

A full log can be found at /root/RHEL83-64_K4.18.0_GCC8.3.1/x86_64-native-linuxapp-gcc/4491e11f4233453a8ab6a429d9afbd2d/dpdk/x86_64-native-linuxapp-gcc/meson-logs/meson-log.txt


*Build Failed #2:
OS: UB2004-32
Target: i686-native-linuxapp-icc



*Build Failed #3:
OS: RHEL83-64
Target: x86_64-native-linuxapp-clang
Program binutils-avx512-check.sh found: YES (/root/RHEL83-64_K4.18.0_Clang11.0.0/x86_64-native-linuxapp-clang/4491e11f4233453a8ab6a429d9afbd2d/dpdk/buildtools/binutils-avx512-check.sh)
Program python3 found: YES (/usr/bin/python3)

buildtools/meson.build:45:8: ERROR: Problem encountered: missing python module: elftools

A full log can be found at /root/RHEL83-64_K4.18.0_Clang11.0.0/x86_64-native-linuxapp-clang/4491e11f4233453a8ab6a429d9afbd2d/dpdk/x86_64-native-linuxapp-clang/meson-logs/meson-log.txt


*Build Failed #4:
OS: RHEL83-64
Target: x86_64-native-linuxapp-gcc+shared
Program binutils-avx512-check.sh found: YES (/root/RHEL83-64_K4.18.0_GCC8.3.1/x86_64-native-linuxapp-gcc+shared/4491e11f4233453a8ab6a429d9afbd2d/dpdk/buildtools/binutils-avx512-check.sh)
Program python3 found: YES (/usr/bin/python3)

buildtools/meson.build:45:8: ERROR: Problem encountered: missing python module: elftools

A full log can be found at /root/RHEL83-64_K4.18.0_GCC8.3.1/x86_64-native-linuxapp-gcc+shared/4491e11f4233453a8ab6a429d9afbd2d/dpdk/x86_64-native-linuxapp-gcc+shared/meson-logs/meson-log.txt


*Build Failed #5:
OS: RHEL83-64
Target: x86_64-native-linuxapp-gcc+debug
Program binutils-avx512-check.sh found: YES (/root/RHEL83-64_K4.18.0_GCC8.3.1/x86_64-native-linuxapp-gcc+debug/4491e11f4233453a8ab6a429d9afbd2d/dpdk/buildtools/binutils-avx512-check.sh)
Program python3 found: YES (/usr/bin/python3)

buildtools/meson.build:45:8: ERROR: Problem encountered: missing python module: elftools

A full log can be found at /root/RHEL83-64_K4.18.0_GCC8.3.1/x86_64-native-linuxapp-gcc+debug/4491e11f4233453a8ab6a429d9afbd2d/dpdk/x86_64-native-linuxapp-gcc+debug/meson-logs/meson-log.txt


*Build Failed #6:
OS: RHEL83-64
Target: x86_64-native-linuxapp-icc

DPDK STV team

             reply	other threads:[~2021-06-29 15:39 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 15:39 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-19 21:15 sys_stv
2023-02-07  8:15 sys_stv
2023-02-07  5:05 sys_stv
2023-01-09  5:34 sys_stv
2022-12-08 21:31 sys_stv
2022-12-06 13:02 sys_stv
2022-12-05  3:36 sys_stv
2022-10-31  5:48 sys_stv
2022-10-11 10:06 sys_stv
2022-09-29  7:48 sys_stv
2022-09-29  5:44 sys_stv
2022-09-29  3:30 sys_stv
2022-09-21 21:06 sys_stv
2022-09-20  9:05 sys_stv
2022-09-19  5:24 sys_stv
2022-09-19  2:38 sys_stv
2022-09-16 10:09 sys_stv
2022-09-15 17:01 sys_stv
2022-09-14 21:06 sys_stv
2022-09-07  8:19 sys_stv
2022-08-30  7:51 sys_stv
2022-08-24  6:11 sys_stv
2022-06-22 21:09 sys_stv
2022-06-09  9:08 sys_stv
2022-06-06  7:26 sys_stv
2022-06-06  2:06 sys_stv
2022-06-01 21:06 sys_stv
2022-06-01  1:57 sys_stv
2022-05-31 21:06 sys_stv
2022-05-30  8:26 sys_stv
2022-05-26  8:57 sys_stv
2022-05-20  5:13 sys_stv
2022-05-20  4:47 sys_stv
2022-05-18 21:07 sys_stv
2022-05-18 10:08 sys_stv
2022-05-17 21:07 sys_stv
2022-05-17  9:36 sys_stv
2022-05-17  9:15 sys_stv
2022-05-17  8:58 sys_stv
2022-05-16 21:06 sys_stv
2022-05-07  7:26 sys_stv
2022-05-06 21:06 sys_stv
2022-05-06  9:49 sys_stv
2022-05-06  9:32 sys_stv
2022-03-08 21:07 sys_stv
2022-03-08 17:16 sys_stv
2022-01-21  7:59 sys_stv
2022-01-21  7:55 sys_stv
2021-12-18 21:50 sys_stv
2021-10-22 22:14 sys_stv
2021-10-14  3:03 sys_stv
2021-08-15 22:10 sys_stv
2021-05-27 22:08 sys_stv
2021-05-07  1:05 sys_stv
2021-03-22 22:07 sys_stv
2021-01-28 22:07 sys_stv
2021-01-27 22:07 sys_stv
2021-01-26 22:08 sys_stv
2021-01-26  6:13 sys_stv
2020-11-05 22:08 sys_stv
2020-11-03 22:07 sys_stv
2020-10-20  5:41 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='970444$cg6abe@fmsmga007-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dpdk_sw_eng@intel.com \
    --cc=npg.sw.core.tools.prc@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).