From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136622 [PATCH] [v2] mbuf: replace GCC marker extension w
Date: Tue, 13 Feb 2024 00:17:21 -0800 (PST) [thread overview]
Message-ID: <65cb2591.810a0220.62124.6e12SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136622
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 13 2024 06:45:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:547f294357690ab8501f120457a82919b1217517
136622 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
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
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29124/
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-13 8:17 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 8:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 10:15 dpdklab
2024-02-13 10:05 dpdklab
2024-02-13 9:47 dpdklab
2024-02-13 9:30 dpdklab
2024-02-13 9:24 dpdklab
2024-02-13 9:16 dpdklab
2024-02-13 9:13 dpdklab
2024-02-13 9:13 dpdklab
2024-02-13 9:07 dpdklab
2024-02-13 8:52 dpdklab
2024-02-13 8:37 dpdklab
2024-02-13 8:27 dpdklab
2024-02-13 8:25 dpdklab
2024-02-13 8:24 dpdklab
2024-02-13 8:20 dpdklab
2024-02-13 8:20 dpdklab
2024-02-13 8:20 dpdklab
2024-02-13 8:20 dpdklab
2024-02-13 8:20 dpdklab
2024-02-13 8:19 dpdklab
2024-02-13 8:18 dpdklab
2024-02-13 8:14 dpdklab
2024-02-13 8:13 dpdklab
2024-02-13 8:08 dpdklab
2024-02-13 8:07 dpdklab
2024-02-13 8:06 dpdklab
2024-02-13 8:04 dpdklab
2024-02-13 8:04 dpdklab
2024-02-13 8:03 dpdklab
2024-02-13 8:03 dpdklab
2024-02-13 8:02 dpdklab
2024-02-13 8:01 dpdklab
2024-02-13 8:01 dpdklab
2024-02-13 7:58 dpdklab
2024-02-13 7:56 dpdklab
2024-02-13 7:56 dpdklab
2024-02-13 7:55 dpdklab
2024-02-13 7:54 dpdklab
2024-02-13 7:53 dpdklab
2024-02-13 7:53 dpdklab
2024-02-13 7:52 dpdklab
2024-02-13 7:51 dpdklab
2024-02-13 7:50 dpdklab
2024-02-13 7:50 dpdklab
2024-02-13 7:49 dpdklab
2024-02-13 7:48 dpdklab
2024-02-13 7:43 dpdklab
2024-02-13 7:37 dpdklab
2024-02-13 7:36 dpdklab
2024-02-13 7:34 dpdklab
2024-02-13 7:31 dpdklab
2024-02-13 7:30 dpdklab
2024-02-13 7:29 dpdklab
2024-02-13 7:29 dpdklab
2024-02-13 7:28 dpdklab
2024-02-13 7:27 dpdklab
2024-02-13 7:27 dpdklab
2024-02-13 7:27 dpdklab
2024-02-13 7:25 dpdklab
2024-02-13 7:25 dpdklab
2024-02-13 7:25 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=65cb2591.810a0220.62124.6e12SMTPIN_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).