From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126363 [PATCH] net/idpf: refine devargs parse functions
Date: Fri, 21 Apr 2023 20:50:00 -0700 (PDT) [thread overview]
Message-ID: <64435968.170a0220.c178a.55a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126363
_Testing PASS_
Submitter: Mingxia Liu <mingxia.liu@intel.com>
Date: Friday, April 21 2023 07:14:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5f34cc454df420b9b2da8deb949fb76cba058b87
126363 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26080/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-22 3:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 3:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-22 6:53 dpdklab
2023-04-22 6:52 dpdklab
2023-04-22 5:46 dpdklab
2023-04-22 4:31 dpdklab
2023-04-22 3:54 dpdklab
2023-04-22 3:42 dpdklab
2023-04-22 3:39 dpdklab
2023-04-22 3:32 dpdklab
2023-04-22 3:20 dpdklab
2023-04-22 3:18 dpdklab
2023-04-22 3:15 dpdklab
2023-04-22 3:13 dpdklab
2023-04-22 3:12 dpdklab
2023-04-22 3:11 dpdklab
2023-04-22 3:09 dpdklab
2023-04-22 2:52 dpdklab
2023-04-22 2:29 dpdklab
2023-04-22 2:25 dpdklab
2023-04-22 2:21 dpdklab
2023-04-22 2:17 dpdklab
2023-04-22 2:16 dpdklab
2023-04-22 2:12 dpdklab
2023-04-22 2:11 dpdklab
2023-04-22 2:09 dpdklab
2023-04-22 2:09 dpdklab
2023-04-22 2:04 dpdklab
2023-04-22 2:03 dpdklab
2023-04-22 2:01 dpdklab
[not found] <20230421071456.297774-1-mingxia.liu@intel.com>
2023-04-21 8:02 ` qemudev
2023-04-21 8:06 ` qemudev
2023-04-21 8:14 ` checkpatch
2023-04-21 8:59 ` 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=64435968.170a0220.c178a.55a2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).