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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] b0b971bf661967fdf3d06e56b5437a779c2915ae
Date: Wed, 17 Apr 2024 22:26:10 -0700 (PDT)	[thread overview]
Message-ID: <6620aef2.0d0a0220.62454.2310SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v23.11

b0b971bf661967fdf3d06e56b5437a779c2915ae --> testing fail

Test environment and result as below:

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

==== 20 line log output for Debian 12 (dpdk_unit_test): ====

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

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

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.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/tarballs/28861/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-04-18  5:26 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  5:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-07  7:55 dpdklab
2024-05-07  7:44 dpdklab
2024-05-07  7:43 dpdklab
2024-05-07  7:41 dpdklab
2024-05-07  7:33 dpdklab
2024-05-07  7:32 dpdklab
2024-05-07  7:31 dpdklab
2024-05-07  7:29 dpdklab
2024-05-07  7:28 dpdklab
2024-05-07  7:22 dpdklab
2024-05-07  7:07 dpdklab
2024-05-07  7:03 dpdklab
2024-05-07  6:32 dpdklab
2024-05-07  6:17 dpdklab
2024-05-04 10:04 dpdklab
2024-05-04  9:44 dpdklab
2024-05-01  5:04 dpdklab
2024-05-01  4:41 dpdklab
2024-05-01  4:37 dpdklab
2024-04-29  5:14 dpdklab
2024-04-29  5:12 dpdklab
2024-04-29  5:10 dpdklab
2024-04-29  5:09 dpdklab
2024-04-29  5:09 dpdklab
2024-04-29  5:08 dpdklab
2024-04-29  5:07 dpdklab
2024-04-29  5:05 dpdklab
2024-04-29  5:00 dpdklab
2024-04-29  4:59 dpdklab
2024-04-29  4:57 dpdklab
2024-04-29  4:56 dpdklab
2024-04-26  6:37 dpdklab
2024-04-18  5:50 dpdklab
2024-04-18  5:43 dpdklab
2024-04-18  5:42 dpdklab
2024-04-18  5:40 dpdklab
2024-04-18  5:37 dpdklab
2024-04-18  5:37 dpdklab
2024-04-18  5:35 dpdklab
2024-04-18  5:34 dpdklab
2024-04-18  5:34 dpdklab
2024-04-18  5:33 dpdklab
2024-04-18  5:31 dpdklab
2024-04-18  5:29 dpdklab
2024-04-18  5:28 dpdklab
2024-04-18  5:10 dpdklab
2024-04-17  5:23 dpdklab
2024-04-17  5:22 dpdklab
2024-04-17  5:22 dpdklab
2024-04-17  5:20 dpdklab
2024-04-17  5:20 dpdklab
2024-04-17  5:19 dpdklab
2024-04-17  5:17 dpdklab
2024-04-17  5:15 dpdklab
2024-04-17  5:15 dpdklab
2024-04-17  5:14 dpdklab
2024-04-17  5:12 dpdklab
2024-04-17  5:08 dpdklab
2024-04-17  5:05 dpdklab
2024-04-17  5:04 dpdklab
2024-04-17  4:44 dpdklab
2024-04-09  5:53 dpdklab
2024-04-09  5:44 dpdklab
2024-04-09  5:32 dpdklab
2024-04-09  5:31 dpdklab
2024-04-09  5:31 dpdklab
2024-04-09  5:27 dpdklab
2024-04-09  5:21 dpdklab
2024-04-09  5:18 dpdklab
2024-04-09  5:17 dpdklab
2024-04-09  5:17 dpdklab
2024-04-09  5:16 dpdklab
2024-04-09  5:12 dpdklab
2024-04-03  1:12 dpdklab
2024-03-30  7:00 dpdklab
2024-03-27  8:36 dpdklab
2024-03-27  7:56 dpdklab
2024-03-27  7:55 dpdklab
2024-03-27  7:54 dpdklab
2024-03-27  7:53 dpdklab
2024-03-27  7:37 dpdklab
2024-03-27  7:35 dpdklab
2024-03-27  7:32 dpdklab
2024-03-27  7:30 dpdklab
2024-03-27  7:08 dpdklab
2024-03-27  7:08 dpdklab
2024-03-27  7:05 dpdklab
2024-03-27  6:58 dpdklab
2024-03-27  5:41 dpdklab
2024-03-25  5:20 dpdklab
2024-03-25  5:08 dpdklab
2024-03-25  5:05 dpdklab
2024-03-25  5:04 dpdklab
2024-03-25  5:03 dpdklab
2024-03-25  5:00 dpdklab
2024-03-25  5:00 dpdklab
2024-03-25  5:00 dpdklab
2024-03-25  4:59 dpdklab
2024-03-25  4:48 dpdklab
2024-03-25  4:43 dpdklab
2024-03-25  4:41 dpdklab
2024-03-25  4:39 dpdklab
2024-03-16  7:11 dpdklab
2024-03-16  6:34 dpdklab
2024-03-16  6:01 dpdklab
2024-03-16  5:50 dpdklab
2024-03-16  5:46 dpdklab
2024-03-16  5:41 dpdklab
2024-03-16  5:35 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=6620aef2.0d0a0220.62454.2310SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.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).