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: 26 Jan 2021 14:08:00 -0800	[thread overview]
Message-ID: <925d15$bi1khh@orsmga008-auth.jf.intel.com> (raw)

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


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


commit 6a2cf58a045f58c9744194f4d44394c7af1a0027
Author: Dong Zhou <dongzhou@nvidia.com>
Date:   Tue Jan 19 05:39:40 2021 +0200

    app/flow-perf: support meter action

DPDK git Repo: dpdk 


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

+------------------+------------+--------------+------------+------------+-----------+----------+
| os               | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+------------------+------------+--------------+------------+------------+-----------+----------+
| UB2004-64        | pass       | pass         | pass       |            |           | pass     |
| RHEL83-64        | pass       |              |            |            |           |          |
| FC33-64          | pass       | pass         |            |            |           |          |
| CentOsStream8-64 | pass       |              |            |            |           |          |
| UB2010-64        | pass       |              |            |            |           |          |
| WIN10-64         |            | FAIL         |            |            |           |          |
| UB2004-32        | pass       |              |            |            |           |          |
| CENTOS83-64      | pass       | pass         | pass       | 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.6.0-050600-generic
	CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
	GCC Version: gcc (Ubuntu 10-20200416-0ubuntu1) 10.0.1 20200416 (experimental) [master revision 3c3f12e2a76:dcee354ce56:44b326839d864fc10c459916abcc97f35a9ac3de]
	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
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	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

OS: FC33-64
	Kernel Version: 5.8.16-300.fc33.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 10.2.1 20201005 (Red Hat 10.2.1-5)
	Clang Version: 11.0.0 (Fedora 11.0.0-1.fc33)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: CentOsStream8-64
	Kernel Version: 4.18.0-257.el8.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
	Clang Version: 11.0.0 (Red Hat 11.0.0-0.2.rc2.module_el8.4.0+533+50191577)
	x86_64-native-linuxapp-gcc

OS: UB2010-64
	Kernel Version: 5.8.0-25-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0
	Clang Version: 11.0.0-2
	x86_64-native-linuxapp-gcc

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

OS: UB2004-32
	Kernel Version: 5.6.0-050600-generic
	CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
	GCC Version: gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
	Clang Version: 10.0.0-4ubuntu1
	i686-native-linuxapp-gcc

OS: CENTOS83-64
	Kernel Version: 4.18.0-240.1.1.el8_3.x86_64
	CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
	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
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug

OS: FreeBSD1201-64
	Kernel Version: 12.1-RELEASE
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.74-MHz K8-class CPU)
	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
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	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.10.0-051000-generic
	CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
	GCC Version: gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc+shared



*Build Failed #1:
OS: WIN10-64
Target: x86_64-windows-clang
FAILED: drivers/rte_bus_pci.pmd.c 
"C:/Program Files/Python37/Scripts/meson" "--internal" "exe" "--unpickle" "C:/windows-dpdk/dpdk/build/meson-private/meson_exe_python.exe_1a08297c06d54c4c62faed85fb4ae53eb0b4356d.dat"
usage: pmdinfogen.py [-h] format input [input ...] output
pmdinfogen.py: error: the following arguments are required: output
Traceback (most recent call last):
  File "../buildtools/gen-pmdinfo-cfile.py", line 19, in <module>
    subprocess.run(pmdinfogen + paths + [output], check=True)
  File "c:\program files\python37\lib\subprocess.py", line 487, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['c:/program files/python37/python.exe', '../buildtools/pmdinfogen.py', 'coff', 'drivers/rte_bus_pci.pmd.c']' returned non-zero exit status 2.
[155/229] Compiling C object drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_fdir.c.obj
[156/229] Generating rte_bus_vdev.pmd.c with a meson_exe.py custom command
FAILED: drivers/rte_bus_vdev.pmd.c 
"C:/Program Files/Python37/Scripts/meson" "--internal" "exe" "--unpickle" "C:/windows-dpdk/dpdk/build/meson-private/meson_exe_python.exe_b5ab8810892e7f443a62c0bebc05ad8f6e03dcda.dat"
usage: pmdinfogen.py [-h] format input [input ...] output
pmdinfogen.py: error: the following arguments are required: output
Traceback (most recent call last):
  File "../buildtools/gen-pmdinfo-cfile.py", line 19, in <module>
    subprocess.run(pmdinfogen + paths + [output], check=True)
  File "c:\program files\python37\lib\subprocess.py", line 487, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['c:/program files/python37/python.exe', '../buildtools/pmdinfogen.py', 'coff', 'drivers/rte_bus_vdev.pmd.c']' returned non-zero exit status 2.
[157/229] Compiling C object lib/librte_kvargs.a.p/librte_kvargs_rte_kvargs.c.obj
[158/229] Compiling C object lib/librte_telemetry.a.p/librte_telemetry_telemetry_data.c.obj
[159/229] Compiling C object drivers/net/i40e/base/libi40e_base.a.p/i40e_common.c.obj
[160/229] Compiling C object drivers/net/i40e/base/libi40e_base.a.p/i40e_diag.c.obj
[161/229] Compiling C object drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_rxtx.c.obj
[162/229] Compiling C object drivers/net/i40e/base/libi40e_base.a.p/i40e_lan_hmc.c.obj
[163/229] Compiling C object lib/librte_telemetry.a.p/librte_telemetry_telemetry.c.obj
[164/229] Generating rte_mempool_ring.pmd.c with a meson_exe.py custom command
FAILED: drivers/rte_mempool_ring.pmd.c 
"C:/Program Files/Python37/Scripts/meson" "--internal" "exe" "--unpickle" "C:/windows-dpdk/dpdk/build/meson-private/meson_exe_python.exe_0d715149d4d636b44908cd9ead690070e762a503.dat"
usage: pmdinfogen.py [-h] format input [input ...] output
pmdinfogen.py: error: the following arguments are required: output
Traceback (most recent call last):
  File "../buildtools/gen-pmdinfo-cfile.py", line 19, in <module>
    subprocess.run(pmdinfogen + paths + [output], check=True)
  File "c:\program files\python37\lib\subprocess.py", line 487, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['c:/program files/python37/python.exe', '../buildtools/pmdinfogen.py', 'coff', 'drivers/rte_mempool_ring.pmd.c']' returned non-zero exit status 2.
[165/229] Compiling C object drivers/net/i40e/base/libi40e_base.a.p/i40e_nvm.c.obj
[166/229] Compiling C object drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_ethdev.c.obj
[167/229] Compiling C object drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.obj
ninja: build stopped


DPDK STV team

             reply	other threads:[~2021-01-26 22:08 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 22:08 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-06-29 15:39 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  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='925d15$bi1khh@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).