From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130511-130512 [PATCH] [2/2] doc: update security guide
Date: Fri, 18 Aug 2023 10:45:58 -0700 (PDT) [thread overview]
Message-ID: <64dfae56.050a0220.d9465.477bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130512
_Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Friday, August 18 2023 09:29:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130511-130512 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| RHEL8 | 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
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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/27381/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-18 17:46 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-19 5:14 dpdklab
2023-08-19 4:57 dpdklab
2023-08-19 4:53 dpdklab
2023-08-19 4:32 dpdklab
2023-08-19 4:15 dpdklab
2023-08-18 19:12 dpdklab
2023-08-18 19:00 dpdklab
2023-08-18 18:52 dpdklab
2023-08-18 18:50 dpdklab
2023-08-18 18:48 dpdklab
2023-08-18 18:45 dpdklab
2023-08-18 18:44 dpdklab
2023-08-18 18:44 dpdklab
2023-08-18 18:27 dpdklab
2023-08-18 18:24 dpdklab
2023-08-18 18:23 dpdklab
2023-08-18 18:17 dpdklab
2023-08-18 18:16 dpdklab
2023-08-18 18:12 dpdklab
2023-08-18 18:07 dpdklab
2023-08-18 18:05 dpdklab
2023-08-18 17:56 dpdklab
2023-08-18 17:49 dpdklab
2023-08-18 17:45 dpdklab
2023-08-18 17:42 dpdklab
2023-08-18 17:40 dpdklab
2023-08-18 17:37 dpdklab
2023-08-18 17:37 dpdklab
2023-08-18 17:33 dpdklab
2023-08-18 17:32 dpdklab
2023-08-18 17:30 dpdklab
2023-08-18 17:29 dpdklab
2023-08-18 17:26 dpdklab
2023-08-18 17:12 dpdklab
2023-08-18 17:08 dpdklab
2023-08-18 16:58 dpdklab
2023-08-18 16:54 dpdklab
2023-08-18 16:53 dpdklab
2023-08-18 16:52 dpdklab
2023-08-18 16:52 dpdklab
2023-08-18 16:51 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:49 dpdklab
2023-08-18 16:49 dpdklab
2023-08-18 16:49 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:47 dpdklab
2023-08-18 16:15 dpdklab
2023-08-18 16:15 dpdklab
2023-08-18 15:59 dpdklab
2023-08-18 15:57 dpdklab
[not found] <20230818092943.1771-2-anoobj@marvell.com>
2023-08-18 9:31 ` |SUCCESS| pw130511-130512 [PATCH 2/2] " qemudev
2023-08-18 9:35 ` 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=64dfae56.050a0220.d9465.477bSMTPIN_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).