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-next-net-mrvl daily Intel builds
Date: 24 May 2022 15:22:12 -0700	[thread overview]
Message-ID: <003cea$htlbvm@orsmga008-auth.jf.intel.com> (raw)

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


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


commit fbaf2409604ebccc3c21d4480844e6de54e62be3
Author: Shun Hao <shunh@nvidia.com>
Date:   Fri May 13 06:57:38 2022 +0300

    app/testpmd: fix metering and policing command for rfc4115

DPDK git Repo: dpdk-next-net-mrvl 


Meson Build Summary: 23 Builds Done, 22 Successful, 1 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FC36-64      |            | pass         |            |            |           |          |            |
| FreeBSD13-64 | pass       | pass         |            | pass       | pass      |          |            |
| RHEL86-64    | pass       | pass         |            | pass       | pass      |          |            |
| SUSE15-64    | pass       | pass         |            |            |           |          |            |
| UB2004-32    | pass       |              |            |            |           |          |            |
| UB2004-64    | pass       | pass         |            |            |           | fail     |            |
| UB2204-32    | pass       |              |            |            |           |          |            |
| UB2204-64N   | pass       |              |            | pass       |           |          |            |
| UB2204-64    | pass       | pass         |            |            |           | pass     | pass       |
| CentOS79-64  | pass       |              |            |            |           |          |            |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+

Comments: 
Because of DPDK bug (https://bugs.dpdk.org/show_bug.cgi?id=928),
All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier. 
 
Test environment and configuration as below:


OS: FC36-64
	Kernel Version: 5.17.7-300.fc36.x86_64
	GCC Version: gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)
	Clang Version: 14.0.0 (Fedora 14.0.0-1.fc36)
	x86_64-native-linuxapp-clang

OS: FreeBSD13-64
	Kernel Version: 13.0-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
	Clang Version: 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc+debug

OS: RHEL86-64
	Kernel Version: 4.18.0-372.9.1.el8.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
	Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug

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

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

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

OS: UB2204-32
	Kernel Version: 5.15.0-25-generic
	GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
	Clang Version: NA
	i686-native-linuxapp-gcc

OS: UB2204-64N
	Kernel Version: 5.17.5-051705-generic
	GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
	Clang Version: 14.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc+shared

OS: UB2204-64
	Kernel Version: 5.15.0-25-generic
	GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
	Clang Version: 14.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc+16byte
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-doc

OS: CentOS79-64
	Kernel Version: 3.10.0-1160.el7.x86_64
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-gcc



*Build Failed #1:
OS: UB2004-64
Target: x86_64-native-linuxapp-doc
Kernel Version: sh: 0: getcwd() failed: No such file or directory
5.8.0-48-generic
CPU info: sh: 0: getcwd() failed: No such file or directory
 Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: sh: 0: getcwd() failed: No such file or directory
gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
Clang Version: 10.0.0-4ubuntu1

--
[1745/3383] Linking static target drivers/net/ice/base/libice_base.a
[1746/3383] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_generic_flow.c.o
[1747/3383] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_dcf_vf_representor.c.o
ninja: error: mkdir(drivers): No such file or directory
ninja: build stopped: .
DPDK STV team

             reply	other threads:[~2022-05-24 22:22 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 22:22 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-22 13:51 sys_stv
2023-05-17 16:43 sys_stv
2023-05-15 23:35 sys_stv
2023-01-09 23:17 sys_stv
2023-01-09 15:50 sys_stv
2023-01-09  8:03 sys_stv
2022-11-23 23:35 sys_stv
2022-11-23  7:53 sys_stv
2022-10-31  4:24 sys_stv
2022-10-13 22:59 sys_stv
2022-09-20 10:38 sys_stv
2022-09-16 11:39 sys_stv
2022-09-14 22:39 sys_stv
2022-06-26 22:24 sys_stv
2022-06-25 22:22 sys_stv
2022-06-24 22:22 sys_stv
2022-06-16 22:20 sys_stv
2022-06-14  6:40 sys_stv
2022-06-10 22:21 sys_stv
2022-06-09 22:20 sys_stv
2022-06-08 22:21 sys_stv
2022-06-06 22:22 sys_stv
2022-06-01 23:26 sys_stv
2022-06-01 22:21 sys_stv
2022-05-31 23:32 sys_stv
2022-05-31 22:21 sys_stv
2022-05-31 11:37 sys_stv
2022-05-31  5:36 sys_stv
2022-05-30 22:22 sys_stv
2022-05-18 23:39 sys_stv
2022-05-18 22:24 sys_stv
2022-05-17 23:41 sys_stv
2022-05-17 22:24 sys_stv
2022-05-17 17:50 sys_stv
2022-05-17 10:55 sys_stv
2022-05-16 22:35 sys_stv
2022-05-07  5:58 sys_stv
2022-05-06 22:33 sys_stv
2022-01-29  5:58 sys_stv
2022-01-29  5:44 sys_stv
2022-01-29  5:41 sys_stv
2022-01-29  5:29 sys_stv
2022-01-29  4:15 sys_stv
2022-01-29  3:59 sys_stv
2022-01-28 11:43 sys_stv
2022-01-28 10:15 sys_stv
2022-01-28  5:28 sys_stv
2022-01-27 23:37 sys_stv
2022-01-27 17:37 sys_stv
2022-01-27 11:38 sys_stv
2022-01-27  6:00 sys_stv
2022-01-27  5:04 sys_stv
2022-01-27  4:19 sys_stv
2022-01-26 23:04 sys_stv
2022-01-26 17:08 sys_stv
2022-01-26  5:04 sys_stv
2022-01-26  2:38 sys_stv
2022-01-25 22:43 sys_stv
2022-01-25 16:53 sys_stv
2022-01-25  9:08 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='003cea$htlbvm@orsmga008-auth.jf.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).