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,
	Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Subject: |FAILURE| pw139295 [PATCH] app/testpmd: fix lcore ID restriction
Date: Mon, 15 Apr 2024 13:58:33 -0700 (PDT)	[thread overview]
Message-ID: <661d94f9.050a0220.b5547.ece8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240415194631.124343-1-sivaprasad.tummala@amd.com>

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

_Testing issues_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, April 15 2024 19:46:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6db5f91b5e628671c341b833f21ea35e65e9699d

139295 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| Fedora 39           | FAIL           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| Debian 12           | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+
| Ubuntu 22.04        | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_unit_test): ====

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

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

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-15 20:58 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240415194631.124343-1-sivaprasad.tummala@amd.com>
2024-04-15 19:23 ` |SUCCESS| " qemudev
2024-04-15 19:27 ` qemudev
2024-04-15 19:47 ` checkpatch
2024-04-15 20:35 ` dpdklab
2024-04-15 20:36 ` |FAILURE| " dpdklab
2024-04-15 20:36 ` dpdklab
2024-04-15 20:37 ` dpdklab
2024-04-15 20:37 ` dpdklab
2024-04-15 20:37 ` dpdklab
2024-04-15 20:38 ` |SUCCESS| " dpdklab
2024-04-15 20:38 ` dpdklab
2024-04-15 20:39 ` dpdklab
2024-04-15 20:40 ` |FAILURE| " dpdklab
2024-04-15 20:40 ` dpdklab
2024-04-15 20:40 ` dpdklab
2024-04-15 20:40 ` dpdklab
2024-04-15 20:41 ` |SUCCESS| " dpdklab
2024-04-15 20:41 ` dpdklab
2024-04-15 20:41 ` |FAILURE| " dpdklab
2024-04-15 20:41 ` |SUCCESS| " dpdklab
2024-04-15 20:44 ` |FAILURE| " 0-day Robot
2024-04-15 20:45 ` |SUCCESS| " dpdklab
2024-04-15 20:45 ` |FAILURE| " dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` |SUCCESS| " dpdklab
2024-04-15 20:47 ` |FAILURE| " dpdklab
2024-04-15 20:48 ` dpdklab
2024-04-15 20:48 ` dpdklab
2024-04-15 20:48 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:50 ` dpdklab
2024-04-15 20:50 ` dpdklab
2024-04-15 20:50 ` |SUCCESS| " dpdklab
2024-04-15 20:50 ` |WARNING| " dpdklab
2024-04-15 20:50 ` |FAILURE| " dpdklab
2024-04-15 20:51 ` dpdklab
2024-04-15 20:51 ` dpdklab
2024-04-15 20:57 ` |SUCCESS| " dpdklab
2024-04-15 20:57 ` |FAILURE| " dpdklab
2024-04-15 20:58 ` |SUCCESS| " dpdklab
2024-04-15 20:58 ` dpdklab [this message]
2024-04-15 20:58 ` dpdklab
2024-04-15 20:59 ` dpdklab
2024-04-15 20:59 ` dpdklab
2024-04-15 20:59 ` |FAILURE| " dpdklab
2024-04-15 20:59 ` dpdklab
2024-04-15 21:00 ` |SUCCESS| " dpdklab
2024-04-15 21:00 ` dpdklab
2024-04-15 21:00 ` |FAILURE| " dpdklab
2024-04-15 21:00 ` |SUCCESS| " dpdklab
2024-04-15 21:00 ` dpdklab
2024-04-15 21:01 ` |FAILURE| " dpdklab
2024-04-15 21:01 ` dpdklab
2024-04-15 21:01 ` |SUCCESS| " dpdklab
2024-04-15 21:02 ` |FAILURE| " dpdklab
2024-04-15 21:02 ` dpdklab
2024-04-15 21:02 ` |SUCCESS| " dpdklab
2024-04-15 21:02 ` |FAILURE| " dpdklab
2024-04-15 21:03 ` dpdklab
2024-04-15 21:03 ` dpdklab
2024-04-15 21:03 ` dpdklab
2024-04-15 21:08 ` dpdklab
2024-04-15 21:09 ` dpdklab
2024-04-15 21:10 ` dpdklab
2024-04-15 21:38 ` dpdklab
2024-04-15 21:41 ` dpdklab
2024-04-15 21:44 ` |SUCCESS| " dpdklab
2024-04-15 21:50 ` |FAILURE| " dpdklab
2024-04-15 22:16 ` 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=661d94f9.050a0220.b5547.ece8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=Sivaprasad.Tummala@amd.com \
    --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).