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-crypto daily Intel builds
Date: 25 Oct 2022 14:29:25 -0700	[thread overview]
Message-ID: <e2f6d4$ilhbdk@orsmga007-auth.jf.intel.com> (raw)

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


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


commit 1c3af0955b5b24658c33cf390c178decae9da0a4
Author: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date:   Tue Sep 27 13:00:43 2022 +0530

    examples/fips_validation: validate ECDSA

DPDK git Repo: dpdk-next-crypto 


Meson Build Summary: 26 Builds Done, 25 Successful, 1 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FC36-64      | pass       | pass         |            |            |           |          |            |
| FreeBSD13-64 | pass       | pass         |            | pass       | pass      |          |            |
| RHEL86-64    | pass       | pass         |            | pass       | pass      |          |            |
| SUSE15-64    | pass       | pass         |            |            |           |          |            |
| RHEL90-64    | pass       |              |            |            |           |          |            |
| UB2004-64    | pass       | pass         |            |            |           | pass     |            |
| UB2204-32    | pass       |              |            |            |           |          |            |
| UB2204-64N   | pass       |              |            | pass       |           |          |            |
| UB2204-64    | pass       | pass         |            |            |           | pass     | pass       |
| CentOS79-64  | fail       |              |            |            |           |          |            |
| RHEL86-64Rt  | pass       | 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-gcc
	x86_64-native-linuxapp-clang

OS: FreeBSD13-64
	Kernel Version: 13.1-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
	Clang Version: 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
	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.14.21-150400.22-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: RHEL90-64
	Kernel Version: 5.14.0-70.13.1.el9_0.x86_64
	GCC Version: gcc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9)
	Clang Version: 13.0.1 (Red Hat 13.0.1-1.el9)
	x86_64-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: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
	GCC Version: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-gcc

OS: RHEL86-64Rt
	Kernel Version: 4.18.0-372.9.1.rt7.166.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



*Build Failed #1:
OS: CentOS79-64
Target: x86_64-native-linuxapp-gcc
FAILED: examples/dpdk-fips_validation.p/fips_validation_fips_validation_ecdsa.c.o 
gcc -Iexamples/dpdk-fips_validation.p -Iexamples -I../examples -Iexamples/fips_validation -I../examples/fips_validation -I../examples/common -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -Ilib/cmdline -I../lib/cmdline -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-missing-field-initializers -D_GNU_SOURCE -march=native -DUSE_OPENSSL -DALLOW_EXPERIMENTAL_API -MD -MQ examples/dpdk-fips_validation.p/fips_validation_fips_validation_ecdsa.c.o -MF examples/dpdk-fips_validation.p/fips_validation_fips_validation_ecdsa.c.o.d -o examples/dpdk-fips_validation.p/fips_validation_fips_validation_ecdsa.c.o -c ../examples/fips_validation/fips_validation_ecdsa.c
../examples/fips_validation/fips_validation_ecdsa.c:8:24: fatal error: sys/random.h: No such file or directory
 #include <sys/random.h>
                        ^
compilation terminated.
[3418/3569] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_rsa.c.o
[3419/3569] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_sha.c.o
[3420/3569] Linking target examples/dpdk-distributor
[3421/3569] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation.c.o
[3422/3569] Linking target examples/dpdk-ethtool
[3423/3569] Linking target examples/dpdk-bbdev_app
[3424/3569] Linking target examples/dpdk-eventdev_pipeline
[3425/3569] Linking target examples/dpdk-dma
[3426/3569] Compiling C object app/test/dpdk-test.p/test_ring.c.o
ninja: build stopped


DPDK STV team

             reply	other threads:[~2022-10-25 21:29 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 21:29 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-12  5:48 sys_stv
2023-05-24 10:01 sys_stv
2023-05-15 21:48 sys_stv
2023-04-27  9:20 sys_stv
2023-04-26 21:59 sys_stv
2023-02-28  8:18 sys_stv
2023-02-27 21:43 sys_stv
2023-02-27 18:47 sys_stv
2023-02-27 18:17 sys_stv
2023-02-27 17:55 sys_stv
2023-01-09 21:31 sys_stv
2022-12-06 13:21 sys_stv
2022-11-23  9:49 sys_stv
2022-11-23  5:59 sys_stv
2022-11-22  8:32 sys_stv
2022-10-31  6:06 sys_stv
2022-10-28  2:14 sys_stv
2022-10-27 15:17 sys_stv
2022-10-27 11:48 sys_stv
2022-10-27  8:16 sys_stv
2022-10-26  7:34 sys_stv
2022-10-25 19:20 sys_stv
2022-10-25 17:46 sys_stv
2022-10-25  8:39 sys_stv
2022-10-24 21:25 sys_stv
2022-10-24  2:00 sys_stv
2022-10-23 21:22 sys_stv
2022-10-22 21:22 sys_stv
2022-10-21 21:24 sys_stv
2022-10-21 16:13 sys_stv
2022-10-21 15:44 sys_stv
2022-10-13 21:24 sys_stv
2022-10-13 12:58 sys_stv
2022-10-13 10:22 sys_stv
2022-10-13  6:02 sys_stv
2022-10-12 21:26 sys_stv
2022-10-12 20:47 sys_stv
2022-10-10  6:48 sys_stv
2022-10-07 21:23 sys_stv
2022-10-07 13:26 sys_stv
2022-09-29 18:17 sys_stv
2022-09-29  6:15 sys_stv
2022-09-21 21:17 sys_stv
2022-09-20 21:18 sys_stv
2022-09-20  9:21 sys_stv
2022-09-16  3:30 sys_stv
2022-09-12 21:18 sys_stv
2022-09-07  8:32 sys_stv
2022-06-26 21:17 sys_stv
2022-06-25 21:18 sys_stv
2022-06-24 21:18 sys_stv
2022-05-18 23:07 sys_stv
2022-05-18 21:18 sys_stv
2022-05-17 23:08 sys_stv
2022-05-17 21:18 sys_stv
2022-05-17 17:16 sys_stv
2022-05-17 11:28 sys_stv
2022-05-17  9:47 sys_stv
2022-05-16 23:20 sys_stv
2022-05-16 21:27 sys_stv
2022-05-07 21:18 sys_stv
2022-05-07 10:08 sys_stv
2022-05-07  5:21 sys_stv
2022-05-06 23:23 sys_stv
2022-05-06 21:18 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='e2f6d4$ilhbdk@orsmga007-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).