From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Mingjin Ye <mingjinx.ye@intel.com>
Subject: |FAILURE| pw135584 [PATCH] [v3] net/iavf: add diagnostic support in
Date: Tue, 26 Dec 2023 04:04:27 -0800 (PST) [thread overview]
Message-ID: <658ac14b.050a0220.f4b67.048dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/135584
_Testing issues_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Tuesday, December 26 2023 10:07:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135584 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | FAIL | PASS |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Windows Server 2019 (dpdk_meson_compile): ====
../drivers/net/iavf/iavf_ethdev.c:2328:8: error: implicit declaration of function 'strtok_r' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
cur = strtok_r(str2, ",", &tmp);
^
../drivers/net/iavf/iavf_ethdev.c:2328:8: note: did you mean 'strtok_s'?
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\ucrt\string.h:64:29: note: 'strtok_s' declared here
_ACRTIMP char* __cdecl strtok_s(
^
../drivers/net/iavf/iavf_ethdev.c:2328:6: error: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Werror,-Wint-conversion]
cur = strtok_r(str2, ",", &tmp);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/iavf/iavf_ethdev.c:2342:7: error: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Werror,-Wint-conversion]
cur = strtok_r(NULL, ",", &tmp);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
4 errors generated.
[146/817] Compiling C object drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_vf_representor.c.obj
[147/817] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_tm.c.obj
[148/817] Compiling C object drivers/libtmp_rte_net_i40e.a.p/net_i40e_i40e_hash.c.obj
[149/817] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_fsub.c.obj
[150/817] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_rxtx.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28738/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-26 12:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 12:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-26 12:00 dpdklab
2023-12-26 11:59 dpdklab
2023-12-26 11:56 dpdklab
2023-12-26 11:46 dpdklab
2023-12-26 11:43 dpdklab
2023-12-26 11:40 dpdklab
2023-12-26 11:39 dpdklab
2023-12-26 11:39 dpdklab
2023-12-26 11:37 dpdklab
2023-12-26 11:36 dpdklab
2023-12-26 11:33 dpdklab
2023-12-26 11:32 dpdklab
2023-12-26 11:30 dpdklab
2023-12-26 11:26 dpdklab
2023-12-26 11:26 dpdklab
2023-12-26 11:24 dpdklab
2023-12-26 11:23 dpdklab
2023-12-26 11:22 dpdklab
2023-12-26 11:19 dpdklab
2023-12-26 11:15 dpdklab
2023-12-26 11:12 dpdklab
2023-12-26 11:07 dpdklab
2023-12-26 11:01 dpdklab
2023-12-26 11:01 dpdklab
2023-12-26 11:00 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=658ac14b.050a0220.f4b67.048dSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mingjinx.ye@intel.com \
--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).