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| pw136645 [PATCH] examples/pipeline: fix include path for r
Date: Tue, 13 Feb 2024 07:51:19 -0800 (PST)	[thread overview]
Message-ID: <65cb8ff7.050a0220.6ede.769cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: Tuesday, February 13 2024 14:52:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fd8b058b322e034e0ddc05d32e643428785aec2a

136645 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+


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

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

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

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/29133/

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 15:51 UTC|newest]

Thread overview: 124+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 15:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14  4:04 dpdklab
2024-02-14  2:36 dpdklab
2024-02-14  2:30 dpdklab
2024-02-14  1:43 dpdklab
2024-02-14  1:38 dpdklab
2024-02-14  1:25 dpdklab
2024-02-14  1:14 dpdklab
2024-02-14  1:13 dpdklab
2024-02-14  1:09 dpdklab
2024-02-14  1:02 dpdklab
2024-02-14  1:01 dpdklab
2024-02-14  0:54 dpdklab
2024-02-14  0:54 dpdklab
2024-02-14  0:53 dpdklab
2024-02-14  0:52 dpdklab
2024-02-14  0:51 dpdklab
2024-02-14  0:47 dpdklab
2024-02-14  0:46 dpdklab
2024-02-14  0:46 dpdklab
2024-02-14  0:46 dpdklab
2024-02-14  0:45 dpdklab
2024-02-14  0:45 dpdklab
2024-02-14  0:44 dpdklab
2024-02-14  0:44 dpdklab
2024-02-14  0:43 dpdklab
2024-02-14  0:40 dpdklab
2024-02-14  0:40 dpdklab
2024-02-14  0:37 dpdklab
2024-02-14  0:37 dpdklab
2024-02-14  0:36 dpdklab
2024-02-14  0:36 dpdklab
2024-02-14  0:29 dpdklab
2024-02-14  0:23 dpdklab
2024-02-14  0:21 dpdklab
2024-02-14  0:21 dpdklab
2024-02-13 23:21 dpdklab
2024-02-13 23:18 dpdklab
2024-02-13 23:00 dpdklab
2024-02-13 22:56 dpdklab
2024-02-13 22:56 dpdklab
2024-02-13 22:56 dpdklab
2024-02-13 22:55 dpdklab
2024-02-13 22:52 dpdklab
2024-02-13 22:50 dpdklab
2024-02-13 22:50 dpdklab
2024-02-13 22:49 dpdklab
2024-02-13 22:49 dpdklab
2024-02-13 22:48 dpdklab
2024-02-13 22:47 dpdklab
2024-02-13 22:47 dpdklab
2024-02-13 22:46 dpdklab
2024-02-13 22:36 dpdklab
2024-02-13 22:34 dpdklab
2024-02-13 22:27 dpdklab
2024-02-13 22:27 dpdklab
2024-02-13 22:27 dpdklab
2024-02-13 22:26 dpdklab
2024-02-13 17:33 dpdklab
2024-02-13 17:11 dpdklab
2024-02-13 16:53 dpdklab
2024-02-13 16:34 dpdklab
2024-02-13 16:32 dpdklab
2024-02-13 16:14 dpdklab
2024-02-13 16:13 dpdklab
2024-02-13 16:05 dpdklab
2024-02-13 16:05 dpdklab
2024-02-13 16:04 dpdklab
2024-02-13 16:02 dpdklab
2024-02-13 16:01 dpdklab
2024-02-13 16:00 dpdklab
2024-02-13 15:58 dpdklab
2024-02-13 15:58 dpdklab
2024-02-13 15:57 dpdklab
2024-02-13 15:57 dpdklab
2024-02-13 15:55 dpdklab
2024-02-13 15:55 dpdklab
2024-02-13 15:54 dpdklab
2024-02-13 15:54 dpdklab
2024-02-13 15:54 dpdklab
2024-02-13 15:54 dpdklab
2024-02-13 15:54 dpdklab
2024-02-13 15:54 dpdklab
2024-02-13 15:54 dpdklab
2024-02-13 15:53 dpdklab
2024-02-13 15:53 dpdklab
2024-02-13 15:53 dpdklab
2024-02-13 15:53 dpdklab
2024-02-13 15:53 dpdklab
2024-02-13 15:52 dpdklab
2024-02-13 15:52 dpdklab
2024-02-13 15:52 dpdklab
2024-02-13 15:52 dpdklab
2024-02-13 15:52 dpdklab
2024-02-13 15:52 dpdklab
2024-02-13 15:52 dpdklab
2024-02-13 15:51 dpdklab
2024-02-13 15:50 dpdklab
2024-02-13 15:50 dpdklab
2024-02-13 15:50 dpdklab
2024-02-13 15:49 dpdklab
2024-02-13 15:49 dpdklab
2024-02-13 15:49 dpdklab
2024-02-13 15:49 dpdklab
2024-02-13 15:48 dpdklab
2024-02-13 15:48 dpdklab
2024-02-13 15:48 dpdklab
2024-02-13 15:47 dpdklab
2024-02-13 15:47 dpdklab
2024-02-13 15:47 dpdklab
2024-02-13 15:47 dpdklab
2024-02-13 15:47 dpdklab
2024-02-13 15:46 dpdklab
2024-02-13 15:46 dpdklab
2024-02-13 15:45 dpdklab
2024-02-13 15:45 dpdklab
2024-02-13 15:45 dpdklab
2024-02-13 15:45 dpdklab
2024-02-13 15:44 dpdklab
2024-02-13 15:44 dpdklab
2024-02-13 15:44 dpdklab
2024-02-13 15:36 dpdklab
2024-02-13 15:28 dpdklab
2024-02-13 15:28 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=65cb8ff7.050a0220.6ede.769cSMTPIN_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).