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| pw126437 [PATCH] [v3] net/idpf: refine devargs parse functions
Date: Sun, 23 Apr 2023 20:06:35 -0700 (PDT) [thread overview]
Message-ID: <6445f23b.c80a0220.610e7.e849SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126437
_Testing PASS_
Submitter: Mingxia Liu <mingxia.liu@intel.com>
Date: Monday, April 24 2023 10:43:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70cc4e1fed665712e68f2f45d98dda4abc6accda
126437 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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
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/26099/
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-24 3:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 3:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 3:44 dpdklab
2023-04-24 3:44 dpdklab
2023-04-24 3:35 dpdklab
2023-04-24 3:30 dpdklab
2023-04-24 3:29 dpdklab
2023-04-24 3:28 dpdklab
2023-04-24 3:28 dpdklab
2023-04-24 3:27 dpdklab
[not found] <20230424104341.64232-1-mingxia.liu@intel.com>
2023-04-24 2:28 ` |SUCCESS| pw126437 [PATCH v3] " checkpatch
2023-04-24 3:19 ` 0-day Robot
2023-04-25 0:19 ` qemudev
2023-04-25 0:20 ` qemudev
2023-04-24 3:19 |SUCCESS| pw126437 [PATCH] [v3] " dpdklab
2023-04-24 3:19 dpdklab
2023-04-24 3:18 dpdklab
2023-04-24 3:15 dpdklab
2023-04-24 3:09 dpdklab
2023-04-24 3:06 dpdklab
2023-04-24 3:06 dpdklab
2023-04-24 3:05 dpdklab
2023-04-24 3:03 dpdklab
2023-04-24 3:02 dpdklab
2023-04-24 3:02 dpdklab
2023-04-24 3:01 dpdklab
2023-04-24 3:01 dpdklab
2023-04-24 3:01 dpdklab
2023-04-24 3:01 dpdklab
2023-04-24 3:01 dpdklab
2023-04-24 3:01 dpdklab
2023-04-24 2:54 dpdklab
2023-04-24 2:49 dpdklab
2023-04-24 2:48 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=6445f23b.c80a0220.610e7.e849SMTPIN_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).