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: 15 Aug 2021 15:10:13 -0700 [thread overview]
Message-ID: <fa9a2a$ff7sle@fmsmga003-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6551 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_
commit 4ac3f3d76e9507a93bcf48d165ffd3a1faba08bb
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Sun Aug 8 17:23:21 2021 +0200
version: 21.08.0
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 | pass | pass | pass | pass | |
| FC34-64 | pass | pass | | | | |
| UB2104-64 | pass | | | | | |
| WIN10-64 | | fail | | | | |
| UB2004-32 | pass | | | | | |
| 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-305.3.1.el8.x86_64
GCC Version: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
Clang Version: 11.0.0 (Red Hat 11.0.0-1.module_el8.4.0+587+5187cac0)
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
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.16-051116-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: WIN10-64
Target: x86_64-windows-clang
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_10de058ccc57d5a5ef4202a93f1ff03752288375.dat"
while executing ['c:\\program files\\python37\\python.exe', '../buildtools/gen-pmdinfo-cfile.py', 'C:/windows-dpdk/dpdk/build/buildtools', 'llvm-ar', 'C:/windows-dpdk/dpdk/build/drivers/libtmp_rte_bus_vdev.a', 'drivers/rte_bus_vdev.pmd.c', 'c:/program files/python37/python.exe', '../buildtools/pmdinfogen.py', 'coff']
--- stdout ---
--- stderr ---
Traceback (most recent call last):
File "../buildtools/gen-pmdinfo-cfile.py", line 20, in <module>
subprocess.run(pmdinfogen + paths + [output], check=True)
File "c:\program files\python37\lib\tempfile.py", line 805, in __exit__
self.cleanup()
File "c:\program files\python37\lib\tempfile.py", line 809, in cleanup
_shutil.rmtree(self.name)
File "c:\program files\python37\lib\shutil.py", line 513, in rmtree
return _rmtree_unsafe(path, onerror)
File "c:\program files\python37\lib\shutil.py", line 401, in _rmtree_unsafe
onerror(os.rmdir, path, sys.exc_info())
File "c:\program files\python37\lib\shutil.py", line 399, in _rmtree_unsafe
os.rmdir(path)
OSError: [WinError 145] The directory is not empty: 'C:/windows-dpdk/dpdk/build/buildtools\\tmpu7830bm_'
[271/367] Generating rte_mempool_ring_def with a custom command
[272/367] Generating rte_bus_auxiliary.pmd.c with a custom command (wrapped by meson to set PATH)
[273/367] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_fdir.c.obj
[274/367] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_acl_ctrl.c.obj
[275/367] Linking target lib/rte_net-21.dll
Creating library lib\rte_net.lib and object lib\rte_net.exp
[276/367] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_vlan_mode.c.obj
[277/367] Generating rte_bus_pci.pmd.c with a custom command (wrapped by meson to set PATH)
[278/367] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_fdir_filter.c.obj
[279/367] Compiling C object drivers/librte_common_iavf.a.p/meson-generated_.._rte_common_iavf.pmd.c.obj
[280/367] Compiling C object drivers/rte_common_iavf-21.dll.p/meson-generated_.._rte_common_iavf.pmd.c.obj
[281/367] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_acl_filter.c.obj
[282/367] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_ethdev.c.obj
[283/367] Compiling C object drivers/net/ice/libice_avx512_lib.a.p/ice_rxtx_vec_avx512.c.obj
ninja: build stopped
DPDK STV team
next reply other threads:[~2021-08-15 22:10 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 22:10 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-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 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='fa9a2a$ff7sle@fmsmga003-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).