From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136621-136620 [PATCH] [v2,4/4] pipeline: replace zero le
Date: Mon, 12 Feb 2024 15:51:22 -0800 (PST) [thread overview]
Message-ID: <65caaefa.810a0220.94e40.db79SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136620
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, February 12 2024 22:36:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39fbd379aa448fda098575f6052dfcdf1dc8e23b
136621-136620 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29123/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-12 23:51 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 23:51 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 0:41 dpdklab
2024-02-13 0:35 dpdklab
2024-02-13 0:21 dpdklab
2024-02-13 0:10 dpdklab
2024-02-13 0:10 dpdklab
2024-02-13 0:09 dpdklab
2024-02-13 0:04 dpdklab
2024-02-12 23:58 dpdklab
2024-02-12 23:57 dpdklab
2024-02-12 23:56 dpdklab
2024-02-12 23:55 dpdklab
2024-02-12 23:55 dpdklab
2024-02-12 23:54 dpdklab
2024-02-12 23:53 dpdklab
2024-02-12 23:53 dpdklab
2024-02-12 23:52 dpdklab
2024-02-12 23:51 dpdklab
2024-02-12 23:51 dpdklab
2024-02-12 23:50 dpdklab
2024-02-12 23:49 dpdklab
2024-02-12 23:49 dpdklab
2024-02-12 23:48 dpdklab
2024-02-12 23:41 dpdklab
2024-02-12 23:40 dpdklab
2024-02-12 23:35 dpdklab
2024-02-12 23:34 dpdklab
2024-02-12 23:34 dpdklab
2024-02-12 23:33 dpdklab
2024-02-12 23:32 dpdklab
2024-02-12 23:32 dpdklab
2024-02-12 23:31 dpdklab
2024-02-12 23:31 dpdklab
2024-02-12 23:31 dpdklab
2024-02-12 23:31 dpdklab
2024-02-12 23:31 dpdklab
2024-02-12 23:30 dpdklab
2024-02-12 23:30 dpdklab
2024-02-12 23:30 dpdklab
2024-02-12 23:30 dpdklab
2024-02-12 23:29 dpdklab
2024-02-12 23:29 dpdklab
2024-02-12 23:29 dpdklab
2024-02-12 23:29 dpdklab
2024-02-12 23:28 dpdklab
2024-02-12 23:28 dpdklab
2024-02-12 23:26 dpdklab
2024-02-12 23:26 dpdklab
2024-02-12 23:26 dpdklab
2024-02-12 23:26 dpdklab
2024-02-12 23:26 dpdklab
2024-02-12 23:25 dpdklab
2024-02-12 23:25 dpdklab
2024-02-12 23:25 dpdklab
2024-02-12 23:25 dpdklab
2024-02-12 23:24 dpdklab
2024-02-12 23:24 dpdklab
2024-02-12 23:24 dpdklab
2024-02-12 23:16 dpdklab
2024-02-12 23:16 dpdklab
2024-02-12 23:16 dpdklab
2024-02-12 23:15 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=65caaefa.810a0220.94e40.db79SMTPIN_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).