From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137356 [PATCH] doc: replace code blocks with includes in
Date: Tue, 27 Feb 2024 10:29:49 -0800 (PST) [thread overview]
Message-ID: <65de2a1d.920a0220.87f52.df3cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137356
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, February 27 2024 14:21:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137356 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Debian 12 (arm) | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
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 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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
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/29291/
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-27 18:29 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 18:29 dpdklab [this message]
[not found] <20240227142138.1942161-1-david.marchand@redhat.com>
2024-02-27 21:20 ` dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:23 ` dpdklab
2024-02-27 21:23 ` dpdklab
2024-02-27 21:23 ` dpdklab
2024-02-27 21:31 ` dpdklab
2024-02-27 21:32 ` dpdklab
2024-02-27 21:32 ` dpdklab
2024-02-27 21:32 ` dpdklab
2024-02-27 21:33 ` dpdklab
2024-02-27 21:34 ` dpdklab
2024-02-27 21:34 ` dpdklab
2024-02-27 21:39 ` dpdklab
2024-02-27 21:39 ` dpdklab
2024-02-27 21:40 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:43 ` dpdklab
2024-02-27 21:43 ` dpdklab
2024-02-27 21:44 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:47 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:51 ` dpdklab
2024-02-27 21:51 ` dpdklab
2024-02-27 21:51 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:54 ` dpdklab
2024-02-27 22:01 ` dpdklab
2024-02-27 22:04 ` dpdklab
2024-02-27 22:04 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:08 ` dpdklab
2024-02-27 22:08 ` dpdklab
2024-02-27 22:09 ` dpdklab
2024-02-27 22:09 ` dpdklab
2024-02-27 22:10 ` dpdklab
2024-02-27 22:19 ` dpdklab
2024-02-27 22:19 ` dpdklab
2024-02-27 22:20 ` dpdklab
2024-02-27 22:29 ` dpdklab
2024-02-27 22:40 ` dpdklab
2024-02-27 22:49 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-28 4:27 ` dpdklab
2024-02-28 4:49 ` dpdklab
2024-02-28 8:26 ` dpdklab
2024-02-28 8:43 ` dpdklab
2024-02-28 8:51 ` dpdklab
2024-02-28 9:25 ` dpdklab
2024-02-28 12:52 ` dpdklab
2024-02-28 14:29 ` dpdklab
2024-02-28 22:21 ` dpdklab
2024-02-28 23:58 ` dpdklab
2024-02-29 12:05 ` dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:13 ` dpdklab
2024-02-29 12:31 ` dpdklab
2024-02-29 12:35 ` dpdklab
2024-02-29 12:37 ` dpdklab
2024-02-29 12:39 ` dpdklab
2024-02-29 12:42 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 19:09 dpdklab
2024-02-27 18:47 dpdklab
2024-02-27 18:47 dpdklab
2024-02-27 18:41 dpdklab
2024-02-27 18:39 dpdklab
2024-02-27 18:30 dpdklab
2024-02-27 18:27 dpdklab
2024-02-27 18:26 dpdklab
2024-02-27 18:25 dpdklab
2024-02-27 18:24 dpdklab
2024-02-27 18:21 dpdklab
2024-02-27 18:21 dpdklab
2024-02-27 18:20 dpdklab
2024-02-27 18:20 dpdklab
2024-02-27 18:19 dpdklab
2024-02-27 18:19 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:17 dpdklab
2024-02-27 18:17 dpdklab
2024-02-27 18:12 dpdklab
2024-02-27 18:11 dpdklab
2024-02-27 17:58 dpdklab
2024-02-27 17:57 dpdklab
2024-02-27 17:55 dpdklab
2024-02-27 17:42 dpdklab
2024-02-27 17:40 dpdklab
2024-02-27 17:37 dpdklab
2024-02-27 17:35 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=65de2a1d.920a0220.87f52.df3cSMTPIN_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).