From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136121-136129 [PATCH] [9/9] security: use C11 alignof
Date: Wed, 24 Jan 2024 17:56:24 -0800 (PST) [thread overview]
Message-ID: <65b1bfc8.050a0220.7b582.d83bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136129
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, January 24 2024 23:17:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1
136121-136129 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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
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
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28959/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-25 1:56 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 1:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 17:14 dpdklab
2024-01-26 17:13 dpdklab
2024-01-25 5:41 dpdklab
2024-01-25 4:48 dpdklab
2024-01-25 3:32 dpdklab
2024-01-25 2:57 dpdklab
2024-01-25 2:24 dpdklab
2024-01-25 2:23 dpdklab
2024-01-25 2:19 dpdklab
2024-01-25 2:19 dpdklab
2024-01-25 2:17 dpdklab
2024-01-25 2:15 dpdklab
2024-01-25 2:15 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:12 dpdklab
2024-01-25 2:12 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:08 dpdklab
2024-01-25 2:07 dpdklab
2024-01-25 2:07 dpdklab
2024-01-25 2:06 dpdklab
2024-01-25 2:06 dpdklab
2024-01-25 2:06 dpdklab
2024-01-25 2:05 dpdklab
2024-01-25 2:05 dpdklab
2024-01-25 2:05 dpdklab
2024-01-25 2:04 dpdklab
2024-01-25 2:02 dpdklab
2024-01-25 2:01 dpdklab
2024-01-25 1:59 dpdklab
2024-01-25 1:59 dpdklab
2024-01-25 1:56 dpdklab
2024-01-25 1:56 dpdklab
2024-01-25 1:55 dpdklab
2024-01-25 1:43 dpdklab
2024-01-25 1:42 dpdklab
2024-01-25 1:41 dpdklab
2024-01-25 1:40 dpdklab
2024-01-25 1:36 dpdklab
2024-01-25 1:36 dpdklab
2024-01-25 1:33 dpdklab
2024-01-25 1:22 dpdklab
2024-01-25 1:19 dpdklab
2024-01-25 1:19 dpdklab
2024-01-25 1:16 dpdklab
2024-01-25 1:14 dpdklab
2024-01-25 1:12 dpdklab
2024-01-25 1:10 dpdklab
2024-01-25 1:08 dpdklab
2024-01-25 1:08 dpdklab
2024-01-25 1:08 dpdklab
[not found] <1706138276-28224-10-git-send-email-roretzla@linux.microsoft.com>
2024-01-24 22:56 ` |SUCCESS| pw136121-136129 [PATCH 9/9] " qemudev
2024-01-24 23:00 ` qemudev
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=65b1bfc8.050a0220.7b582.d83bSMTPIN_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).