automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jie Hai <haijie1@huawei.com>
Subject: |FAILURE| pw134132-134152 [PATCH] [21/21] examples/vhost: replace st
Date: Mon, 13 Nov 2023 07:19:42 -0800 (PST)	[thread overview]
Message-ID: <65523e8e.050a0220.23374.49caSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/134152

_Testing issues_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Monday, November 13 2023 10:45:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d677a3eb1b4e2d38c193fabd755dac30ee04c2df

134132-134152 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | FAIL               | PASS                 |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+

==== 20 line log output for Windows Server 2019 (dpdk_meson_compile): ====
../lib/ethdev/rte_ethdev_telemetry.c:493:15: 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(
^
../lib/ethdev/rte_ethdev_telemetry.c:493:13: error: incompatible integer to pointer conversion assigning to 'const char *' from 'int' [-Werror,-Wint-conversion]
qid_param = strtok_r(end_param, ",", &sp);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/ethdev/rte_ethdev_telemetry.c:1228:18: error: implicit declaration of function 'strtok_r' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
splited_param = strtok_r(params, ",", &sp);
^
../lib/ethdev/rte_ethdev_telemetry.c:1228:16: error: incompatible integer to pointer conversion assigning to 'const char *' from 'int' [-Werror,-Wint-conversion]
splited_param = strtok_r(params, ",", &sp);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~
4 errors generated.
[12/815] Compiling C object lib/librte_ethdev.a.p/ethdev_ethdev_private.c.obj
[13/815] Compiling C object lib/librte_ethdev.a.p/ethdev_sff_common.c.obj
[14/815] Compiling C object lib/librte_ethdev.a.p/ethdev_rte_ethdev_cman.c.obj
[15/815] Compiling C object lib/librte_ethdev.a.p/ethdev_ethdev_profile.c.obj
[16/815] Compiling C object lib/librte_ethdev.a.p/ethdev_ethdev_trace_points.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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/28348/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-11-13 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 15:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-13 16:08 dpdklab
2023-11-13 15:26 dpdklab
2023-11-13 15:24 dpdklab
2023-11-13 15:23 dpdklab
2023-11-13 15:23 dpdklab
2023-11-13 15:23 dpdklab
2023-11-13 15:19 dpdklab
2023-11-13 15:19 dpdklab
2023-11-13 15:19 dpdklab
2023-11-13 15:19 dpdklab
2023-11-13 15:19 dpdklab
2023-11-13 15:19 dpdklab
2023-11-13 14:47 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=65523e8e.050a0220.23374.49caSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=haijie1@huawei.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).