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
Subject: |SUCCESS| pw136649-136648 [PATCH] [3/3] examples/pipeline: add examp
Date: Tue, 13 Feb 2024 09:51:03 -0800 (PST)	[thread overview]
Message-ID: <65cbac07.050a0220.74cf7.3260SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136648

_Testing PASS_

Submitter: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: Tuesday, February 13 2024 16:57:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31d72ff4dc7c057366153e9918ac92bf9123a3bc

136649-136648 --> testing pass

Test environment and result as below:

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


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

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

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

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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.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)

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-13 17:51 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 17:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14  2:37 dpdklab
2024-02-14  1:40 dpdklab
2024-02-14  1:27 dpdklab
2024-02-14  0:38 dpdklab
2024-02-14  0:37 dpdklab
2024-02-14  0:37 dpdklab
2024-02-14  0:36 dpdklab
2024-02-14  0:26 dpdklab
2024-02-14  0:24 dpdklab
2024-02-14  0:22 dpdklab
2024-02-14  0:22 dpdklab
2024-02-14  0:21 dpdklab
2024-02-14  0:20 dpdklab
2024-02-14  0:20 dpdklab
2024-02-14  0:20 dpdklab
2024-02-14  0:20 dpdklab
2024-02-14  0:18 dpdklab
2024-02-14  0:17 dpdklab
2024-02-14  0:12 dpdklab
2024-02-14  0:11 dpdklab
2024-02-14  0:05 dpdklab
2024-02-14  0:04 dpdklab
2024-02-14  0:02 dpdklab
2024-02-13 23:55 dpdklab
2024-02-13 23:52 dpdklab
2024-02-13 23:46 dpdklab
2024-02-13 23:45 dpdklab
2024-02-13 23:42 dpdklab
2024-02-13 23:42 dpdklab
2024-02-13 23:40 dpdklab
2024-02-13 23:37 dpdklab
2024-02-13 23:36 dpdklab
2024-02-13 23:33 dpdklab
2024-02-13 23:29 dpdklab
2024-02-13 23:24 dpdklab
2024-02-13 23:00 dpdklab
2024-02-13 22:54 dpdklab
2024-02-13 22:52 dpdklab
2024-02-13 22:50 dpdklab
2024-02-13 22:47 dpdklab
2024-02-13 22:46 dpdklab
2024-02-13 22:44 dpdklab
2024-02-13 22:44 dpdklab
2024-02-13 22:44 dpdklab
2024-02-13 22:39 dpdklab
2024-02-13 22:38 dpdklab
2024-02-13 22:38 dpdklab
2024-02-13 22:37 dpdklab
2024-02-13 22:36 dpdklab
2024-02-13 22:36 dpdklab
2024-02-13 22:35 dpdklab
2024-02-13 22:34 dpdklab
2024-02-13 22:34 dpdklab
2024-02-13 22:34 dpdklab
2024-02-13 22:33 dpdklab
2024-02-13 22:29 dpdklab
2024-02-13 22:27 dpdklab
2024-02-13 22:22 dpdklab
2024-02-13 17:58 dpdklab
2024-02-13 17:53 dpdklab
2024-02-13 17:52 dpdklab
2024-02-13 17:52 dpdklab
2024-02-13 17:51 dpdklab
2024-02-13 17:50 dpdklab
2024-02-13 17:50 dpdklab
2024-02-13 17:50 dpdklab
2024-02-13 17:50 dpdklab
2024-02-13 17:50 dpdklab
2024-02-13 17:50 dpdklab
2024-02-13 17:49 dpdklab
2024-02-13 17:49 dpdklab
2024-02-13 17:49 dpdklab
2024-02-13 17:49 dpdklab
2024-02-13 17:49 dpdklab
2024-02-13 17:49 dpdklab
2024-02-13 17:49 dpdklab
2024-02-13 17:48 dpdklab
2024-02-13 17:48 dpdklab
2024-02-13 17:48 dpdklab
2024-02-13 17:48 dpdklab
2024-02-13 17:48 dpdklab
2024-02-13 17:47 dpdklab
2024-02-13 17:46 dpdklab
2024-02-13 17:46 dpdklab
2024-02-13 17:46 dpdklab
2024-02-13 17:45 dpdklab
2024-02-13 17:44 dpdklab
2024-02-13 17:44 dpdklab
2024-02-13 17:44 dpdklab
2024-02-13 17:44 dpdklab
2024-02-13 17:43 dpdklab
2024-02-13 17:43 dpdklab
2024-02-13 17:43 dpdklab
2024-02-13 17:43 dpdklab
2024-02-13 17:43 dpdklab
2024-02-13 17:42 dpdklab
2024-02-13 17:42 dpdklab
2024-02-13 17:42 dpdklab
2024-02-13 17:37 dpdklab
2024-02-13 17:37 dpdklab
2024-02-13 17:36 dpdklab
2024-02-13 17:36 dpdklab
2024-02-13 17:36 dpdklab
2024-02-13 17:35 dpdklab
2024-02-13 17:35 dpdklab
2024-02-13 17:35 dpdklab
2024-02-13 17:35 dpdklab
2024-02-13 17:35 dpdklab
2024-02-13 17:34 dpdklab
2024-02-13 17:34 dpdklab
2024-02-13 17:34 dpdklab
2024-02-13 17:34 dpdklab
2024-02-13 17:34 dpdklab
2024-02-13 17:31 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=65cbac07.050a0220.74cf7.3260SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).