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| pw125877-125889 [PATCH] [13/13] net/nfp: modify the logic of some NFDk function
Date: Mon, 10 Apr 2023 12:17:43 +0000 (UTC) [thread overview]
Message-ID: <20230410121743.2A92E60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125889
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, April 10 2023 11:00:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125877-125889 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25947/
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-10 12:17 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 12:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-10 19:00 dpdklab
2023-04-10 13:41 dpdklab
2023-04-10 13:33 dpdklab
2023-04-10 13:29 dpdklab
2023-04-10 13:13 dpdklab
2023-04-10 13:09 dpdklab
2023-04-10 13:04 dpdklab
2023-04-10 13:04 dpdklab
2023-04-10 13:02 dpdklab
2023-04-10 13:00 dpdklab
2023-04-10 12:59 dpdklab
2023-04-10 12:59 dpdklab
2023-04-10 12:51 dpdklab
2023-04-10 12:47 dpdklab
2023-04-10 12:47 dpdklab
2023-04-10 12:39 dpdklab
2023-04-10 12:36 dpdklab
2023-04-10 12:36 dpdklab
2023-04-10 12:29 dpdklab
2023-04-10 12:24 dpdklab
2023-04-10 12:23 dpdklab
2023-04-10 12:22 dpdklab
2023-04-10 12:20 dpdklab
2023-04-10 12:19 dpdklab
2023-04-10 12:18 dpdklab
2023-04-10 12:18 dpdklab
2023-04-10 12:17 dpdklab
2023-04-10 12:16 dpdklab
2023-04-10 12:16 dpdklab
2023-04-10 12:15 dpdklab
2023-04-10 12:12 dpdklab
2023-04-10 12:11 dpdklab
2023-04-10 12:10 dpdklab
2023-04-10 12:03 dpdklab
2023-04-10 12:01 dpdklab
2023-04-10 12:00 dpdklab
2023-04-10 12:00 dpdklab
2023-04-10 11:59 dpdklab
2023-04-10 11:57 dpdklab
2023-04-10 11:55 dpdklab
2023-04-10 11:52 dpdklab
2023-04-10 11:51 dpdklab
2023-04-10 11:50 dpdklab
2023-04-10 11:50 dpdklab
2023-04-10 11:50 dpdklab
2023-04-10 11:47 dpdklab
2023-04-10 11:46 dpdklab
2023-04-10 11:46 dpdklab
2023-04-10 11:44 dpdklab
2023-04-10 11:44 dpdklab
2023-04-10 11:39 dpdklab
2023-04-10 11:37 dpdklab
[not found] <20230410110015.2973660-14-chaoyong.he@corigine.com>
2023-04-10 10:52 ` |SUCCESS| pw125877-125889 [PATCH 13/13] " qemudev
2023-04-10 10:56 ` 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=20230410121743.2A92E60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--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).