From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw91702-91700 [PATCH] [v2, 7/7] examples/vhost_blk: support set ctrl worker thread name
Date: Sun, 18 Apr 2021 20:07:14 -0400 (EDT) [thread overview]
Message-ID: <20210419000714.0F1EF3055B@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 5582 bytes --]
Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/91700
_Testing issues_
Submitter: Min Hu (Connor) <humin29@huawei.com>
Date: Saturday, April 17 2021 09:09:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b729b3c039c40e322e0b078e7394e4bdfea8862f
91702-91700 --> testing fail
Test environment and result as below:
+---------------------+----------------------+--------------------+-------------------+----------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_compile_spdk | dpdk_unit_test |
+=====================+======================+====================+===================+================+
| Windows Server 2019 | PASS | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| FreeBSD 11.2 | SKIPPED | FAIL | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Fedora 31 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Fedora 32 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| CentOS Stream 8 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 | SKIPPED | PASS | PASS | PASS |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 20.04 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Arch Linux | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| RHEL8 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| RHEL 7 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| openSUSE Leap 15 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 ARM | SKIPPED | PASS | SKIPPED | PASS |
+---------------------+----------------------+--------------------+-------------------+----------------+
==== 20 line log output for FreeBSD 11.2 (dpdk_meson_compile): ====
pthread_setname_np(t_old, "telemetry-v1");
^
../lib/librte_telemetry/telemetry.c:445:2: note: did you mean 'pthread_set_name_np'?
/usr/include/pthread_np.h:58:6: note: 'pthread_set_name_np' declared here
void pthread_set_name_np(pthread_t, const char *);
^
../lib/librte_telemetry/telemetry.c:445:2: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes]
pthread_setname_np(t_old, "telemetry-v1");
^
../lib/librte_telemetry/telemetry.c:474:2: error: implicit declaration of function 'pthread_setname_np' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
pthread_setname_np(t_new, "telemetry-v2");
^
3 errors generated.
[9/2106] Compiling C object lib/librte_eal.a.p/librte_eal_common_eal_common_cpuflags.c.o
[10/2106] Compiling C object lib/librte_telemetry.a.p/librte_telemetry_telemetry_legacy.c.o
[11/2106] Compiling C object lib/librte_eal.a.p/librte_eal_common_eal_common_bus.c.o
[12/2106] Compiling C object lib/librte_eal.a.p/librte_eal_common_eal_common_class.c.o
[13/2106] Generating kvargs.sym_chk with a meson_exe.py custom command
ninja: build stopped: subcommand failed.
[1] Error running command.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0 and gcc 8.1.0 (MinGW)
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
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
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Arch Linux
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/16601/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-04-19 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210419000714.0F1EF3055B@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@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).