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, "Varghese,
	Vipin" <vipin.varghese@amd.com>
Subject: |FAILURE| pw143403-143404 [PATCH] [RFC,2/2] eal/lcore: add llc aware
Date: Tue, 27 Aug 2024 09:10:37 -0700 (PDT)	[thread overview]
Message-ID: <66cdfa7d.170a0220.139577.d320SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240827151014.201-3-vipin.varghese@amd.com>

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

_Testing issues_

Submitter: Varghese, Vipin <vipin.varghese@amd.com>
Date: Tuesday, August 27 2024 15:10:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143403-143404 --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#255885

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | WARN           |
+---------------------+----------------+
| Debian Bullseye     | WARN           |
+---------------------+----------------+
| Debian 12           | WARN           |
+---------------------+----------------+
| Fedora 37           | WARN           |
+---------------------+----------------+
| Fedora 38 (Clang)   | WARN           |
+---------------------+----------------+
| Fedora 38           | WARN           |
+---------------------+----------------+
| Fedora 39           | WARN           |
+---------------------+----------------+
| Fedora 39 (Clang)   | WARN           |
+---------------------+----------------+
| Fedora 40           | WARN           |
+---------------------+----------------+
| Fedora 40 (Clang)   | WARN           |
+---------------------+----------------+
| RHEL8               | WARN           |
+---------------------+----------------+
| RHEL9               | WARN           |
+---------------------+----------------+
| Ubuntu 24.04        | WARN           |
+---------------------+----------------+
| Ubuntu 22.04        | WARN           |
+---------------------+----------------+
| Ubuntu 20.04        | WARN           |
+---------------------+----------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_unit_test): ====
|                                                                             char *
In file included from ../lib/eal/common/eal_common_lcore.c:6:
/usr/include/stdlib.h:181:25: note: expected 'char ** restrict' but argument is of type 'char *'
181 |       char **__restrict __endptr, int __base)
|       ~~~~~~~~~~~~~~~~~~^~~~~~~~
../lib/eal/common/eal_common_lcore.c: In function 'rte_get_llc_n_lcore':
../lib/eal/common/eal_common_lcore.c:252:15: error: unused variable 'last_lcore_cpu' [-Werror=unused-variable]
252 |  unsigned int last_lcore_cpu = RTE_MAX_LCORE;
|               ^~~~~~~~~~~~~~
../lib/eal/common/eal_common_lcore.c:251:15: error: unused variable 'first_lcore_cpu' [-Werror=unused-variable]
251 |  unsigned int first_lcore_cpu = RTE_MAX_LCORE;
|               ^~~~~~~~~~~~~~~
../lib/eal/common/eal_common_lcore.c:250:7: error: unused variable 'found_last_cpu' [-Werror=unused-variable]
250 |  bool found_last_cpu = false;
|       ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[27/2939] Generating telemetry.sym_chk with a meson_exe.py custom command.
[28/2939] Generating log.sym_chk with a meson_exe.py custom command.
[29/2939] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_memalloc.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-27 16:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240827151014.201-3-vipin.varghese@amd.com>
2024-08-27 14:44 ` |SUCCESS| pw143403-143404 [RFC 2/2] eal/lcore: add llc aware for each macro qemudev
2024-08-27 14:48 ` qemudev
2024-08-27 15:12 ` |WARNING| pw143404 " checkpatch
2024-08-27 15:54 ` |SUCCESS| pw143403-143404 [PATCH] [RFC,2/2] eal/lcore: add llc aware dpdklab
2024-08-27 15:55 ` dpdklab
2024-08-27 15:58 ` |FAILURE| " dpdklab
2024-08-27 15:58 ` |SUCCESS| " dpdklab
2024-08-27 15:59 ` |FAILURE| " dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 16:00 ` dpdklab
2024-08-27 16:09 ` dpdklab
2024-08-27 16:10 ` dpdklab [this message]
2024-08-27 16:12 ` dpdklab
2024-08-27 16:14 ` |SUCCESS| " dpdklab
2024-08-27 16:16 ` dpdklab
2024-08-27 16:17 ` |FAILURE| " dpdklab
2024-08-27 16:20 ` |WARNING| " dpdklab
2024-08-27 16:24 ` |SUCCESS| " dpdklab
2024-08-27 16:29 ` dpdklab
2024-08-27 16:41 ` |WARNING| " dpdklab
2024-08-27 16:43 ` |FAILURE| pw143404 [RFC 2/2] eal/lcore: add llc aware for each macro 0-day Robot
2024-08-27 16:43 ` |SUCCESS| pw143403-143404 [PATCH] [RFC,2/2] eal/lcore: add llc aware dpdklab
2024-08-27 17:04 ` |WARNING| " dpdklab
2024-08-27 19:51 ` |SUCCESS| " dpdklab
2024-09-19 23:23 ` dpdklab
2024-09-19 23:43 ` 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=66cdfa7d.170a0220.139577.d320SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=vipin.varghese@amd.com \
    /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).