From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| [GIT MASTER] 7001c8fdb27357c67147c0a13cb3826e48c0f2bf
Date: Thu, 17 Jun 2021 19:32:14 -0400 (EDT) [thread overview]
Message-ID: <20210617233214.B57A130681@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 7832 bytes --]
_Testing issues_
Branch: tags/v19.11
7001c8fdb27357c67147c0a13cb3826e48c0f2bf --> testing fail
Test environment and result as below:
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Environment | dpdk_mingw64_compile | dpdk_compile_spdk | dpdk_unit_test | dpdk_meson_compile |
+====================================+======================+===================+================+====================+
| Windows Server 2019 | FAIL | SKIPPED | SKIPPED | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Ubuntu 18.04 | SKIPPED | FAIL | FAIL | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Arch Linux | SKIPPED | SKIPPED | FAIL | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| CentOS Stream 8 | SKIPPED | SKIPPED | FAIL | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| CentOS 8 | SKIPPED | SKIPPED | FAIL | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Fedora 31 | SKIPPED | SKIPPED | FAIL | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Fedora 32 | SKIPPED | SKIPPED | FAIL | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| openSUSE Leap 15 | SKIPPED | SKIPPED | FAIL | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| RHEL 7 | SKIPPED | SKIPPED | FAIL | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| RHEL8 | SKIPPED | SKIPPED | FAIL | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Fedora 34 | SKIPPED | SKIPPED | FAIL | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Ubuntu 20.04 | SKIPPED | SKIPPED | FAIL | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Fedora 33 | SKIPPED | SKIPPED | FAIL | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Fedora 34 clang | SKIPPED | SKIPPED | FAIL | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| FreeBSD 13 | SKIPPED | SKIPPED | SKIPPED | FAIL |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Ubuntu 18.04 ARM | SKIPPED | SKIPPED | SKIPPED | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| FreeBSD 11.2 | SKIPPED | SKIPPED | SKIPPED | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
| Ubuntu 20.04 ARM cross-compilation | SKIPPED | SKIPPED | SKIPPED | PASS |
+------------------------------------+----------------------+-------------------+----------------+--------------------+
==== 20 line log output for Windows Server 2019 (dpdk_mingw64_compile): ====
^
../lib/librte_eal/windows/eal/eal_thread.c:97:41: error: format '%s' expects argument of type 'char *', but argument 5 has type 'long long unsigned int' [-Werror=format=]
lcore_id, (uintptr_t)thread_id, cpuset);
~~~~~~~~~~~~~~~~~~~~ ^
..\lib\librte_eal\common\include/rte_log.h:337:25: note: in definition of macro 'RTE_LOG'
RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
^
../lib/librte_eal/windows/eal/eal_thread.c:97:41: error: too many arguments for format [-Werror=format-extra-args]
lcore_id, (uintptr_t)thread_id, cpuset);
^
..\lib\librte_eal\common\include/rte_log.h:337:25: note: in definition of macro 'RTE_LOG'
RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
^
../lib/librte_eal/windows/eal/eal_thread.c: In function 'eal_thread_create':
../lib/librte_eal/windows/eal/eal_thread.c:145:29: error: cast between incompatible function types from '__attribute__((noreturn)) void * (*)(void *)' to 'DWORD (*)(void *)' {aka 'long unsigned int (*)(void *)'} [-Werror=cast-function-type]
th = CreateThread(NULL, 0, (LPTHREAD_START_ROUTINE)eal_thread_loop,
^
cc1.exe: all warnings being treated as errors
[11/18] Compiling C object lib/librte_eal.a.p/librte_eal_windows_eal_eal.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0 and gcc 8.1.0 (MinGW)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
FreeBSD 13
Kernel: 13.0
Compiler: gcc 10.2.0
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
Ubuntu 20.04 ARM cross-compilation
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/15543/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-06-17 23:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 23:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 16:34 dpdklab
2021-06-25 16:16 dpdklab
2021-06-25 15:33 dpdklab
2021-06-25 14:47 dpdklab
2021-06-25 13:37 dpdklab
2021-06-25 13:13 dpdklab
2021-06-23 20:33 dpdklab
2021-06-23 17:28 dpdklab
2021-06-23 12:15 dpdklab
2021-06-23 7:03 dpdklab
2021-06-22 20:32 dpdklab
2021-06-17 22:51 dpdklab
2021-06-17 22:01 dpdklab
2019-12-02 20:28 dpdklab
2019-12-01 15:36 dpdklab
2019-11-29 19:28 dpdklab
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=20210617233214.B57A130681@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).