From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129697 [PATCH] [v2] doc: update doc for idpf and cpfl
Date: Tue, 25 Jul 2023 01:11:39 -0700 (PDT) [thread overview]
Message-ID: <64bf83bb.170a0220.ead2f.ad72SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129697
_Testing PASS_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Tuesday, July 25 2023 15:25:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d2cfa0c7280051e7e6a385c0c8fa57f7b74f9ea0
129697 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.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)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-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 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27135/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-25 8:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 8:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 18:41 dpdklab
2023-07-25 18:40 dpdklab
2023-07-25 10:19 dpdklab
2023-07-25 8:34 dpdklab
2023-07-25 8:31 dpdklab
2023-07-25 8:27 dpdklab
2023-07-25 8:19 dpdklab
2023-07-25 8:10 dpdklab
2023-07-25 8:06 dpdklab
2023-07-25 8:05 dpdklab
2023-07-25 8:03 dpdklab
2023-07-25 8:01 dpdklab
2023-07-25 7:57 dpdklab
2023-07-25 7:55 dpdklab
2023-07-25 7:54 dpdklab
2023-07-25 7:53 dpdklab
2023-07-25 7:52 dpdklab
2023-07-25 7:45 dpdklab
2023-07-25 7:45 dpdklab
2023-07-25 7:45 dpdklab
2023-07-25 7:45 dpdklab
2023-07-25 7:44 dpdklab
2023-07-25 7:44 dpdklab
2023-07-25 7:43 dpdklab
2023-07-25 7:43 dpdklab
2023-07-25 7:43 dpdklab
2023-07-25 7:42 dpdklab
2023-07-25 7:41 dpdklab
[not found] <20230725152503.5814-1-beilei.xing@intel.com>
2023-07-25 6:53 ` |SUCCESS| pw129697 [PATCH v2] " qemudev
2023-07-25 6:57 ` qemudev
2023-07-25 7:07 ` checkpatch
2023-07-25 7:58 ` 0-day Robot
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=64bf83bb.170a0220.ead2f.ad72SMTPIN_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).