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,
	Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Subject: |FAILURE| pw137172-137175 [PATCH] [RFC,v4,6/6] eal: keep per-lcore p
Date: Sun, 25 Feb 2024 08:02:47 -0800 (PST)	[thread overview]
Message-ID: <65db64a7.810a0220.83df0.b129SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/137175

_Testing issues_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Sunday, February 25 2024 15:03:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137172-137175 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL           |
+---------------------+----------------+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Debian Buster       | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+
| Ubuntu 22.04        | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+
| openSUSE Leap 15    | FAIL           |
+---------------------+----------------+

==== 20 line log output for openSUSE Leap 15 (dpdk_unit_test): ====
[48/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_random.c.o'.
[49/2800] Linking target lib/librte_telemetry.so.24.1.
[50/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_version.c.o'.
[51/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_dynmem.c.o'.
[52/2800] Generating symbol file 'lib/76b5a35@@rte_kvargs@sha/librte_kvargs.so.24.1.symbols'.
[53/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_cpuflags.c.o'.
[54/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_hypervisor.c.o'.
[55/2800] Generating symbol file 'lib/76b5a35@@rte_telemetry@sha/librte_telemetry.so.24.1.symbols'.
[56/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_service.c.o'.
FAILED: lib/76b5a35@@rte_eal@sta/eal_common_rte_service.c.o
ccache cc -Ilib/76b5a35@@rte_eal@sta -Ilib -I../lib -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation '-DABI_VERSION="24.1"' -DRTE_LOG_DEFAULT_LOGTYPE=lib.eal -MD -MQ 'lib/76b5a
 35@@rte_eal@sta/eal_common_rte_service.c.o' -MF 'lib/76b5a35@@rte_eal@sta/eal_common_rte_service.c.o.d' -o 'lib/76b5a35@@rte_eal@sta/eal_common_rte_service.c.o' -c ../lib/eal/common/rte_service.c
../lib/eal/common/rte_service.c: In function 'rte_service_lcore_may_be_active':
../lib/eal/common/rte_service.c:540:35: error: 'cs' may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (lcore >= RTE_MAX_LCORE || !cs->is_service_core)
~~^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[57/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace.c.o'.
[58/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace_ctf.c.o'.
[59/2800] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_proc.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

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

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: gcc 13.1.1

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.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)

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29252/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-25 16:02 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 16:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-25 16:05 dpdklab
2024-02-25 16:04 dpdklab
2024-02-25 16:04 dpdklab
2024-02-25 16:04 dpdklab
2024-02-25 16:04 dpdklab
2024-02-25 16:04 dpdklab
2024-02-25 16:03 dpdklab
2024-02-25 16:03 dpdklab
2024-02-25 16:03 dpdklab
2024-02-25 16:03 dpdklab
2024-02-25 16:02 dpdklab
2024-02-25 16:02 dpdklab
2024-02-25 16:02 dpdklab
2024-02-25 16:01 dpdklab
2024-02-25 16:01 dpdklab
2024-02-25 16:01 dpdklab
2024-02-25 16:01 dpdklab
2024-02-25 16:01 dpdklab
2024-02-25 16:00 dpdklab
2024-02-25 16:00 dpdklab
2024-02-25 15:59 dpdklab
2024-02-25 15:59 dpdklab
2024-02-25 15:59 dpdklab
2024-02-25 15:59 dpdklab
2024-02-25 15:58 dpdklab
2024-02-25 15:58 dpdklab
2024-02-25 15:58 dpdklab
2024-02-25 15:58 dpdklab
2024-02-25 15:58 dpdklab
2024-02-25 15:58 dpdklab
2024-02-25 15:57 dpdklab
2024-02-25 15:57 dpdklab
2024-02-25 15:57 dpdklab
2024-02-25 15:57 dpdklab
2024-02-25 15:57 dpdklab
2024-02-25 15:56 dpdklab
2024-02-25 15:56 dpdklab
2024-02-25 15:55 dpdklab
2024-02-25 15:55 dpdklab
2024-02-25 15:54 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=65db64a7.810a0220.83df0.b129SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mattias.ronnblom@ericsson.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).