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| pw125901-125905 [PATCH] [5/5] mempool/cnxk: add support for exchanging mbufs between pools
Date: Tue, 11 Apr 2023 11:31:41 +0000 (UTC) [thread overview]
Message-ID: <20230411113141.14E5A60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125905
_Testing PASS_
Submitter: Ashwin Sekhar T K <asekhar@marvell.com>
Date: Tuesday, April 11 2023 07:55:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125901-125905 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-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)
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25954/
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-11 11:31 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 11:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 0:01 dpdklab
2023-04-12 23:46 dpdklab
2023-04-12 21:14 dpdklab
2023-04-12 20:55 dpdklab
2023-04-12 20:51 dpdklab
2023-04-11 14:18 dpdklab
2023-04-11 14:16 dpdklab
2023-04-11 14:16 dpdklab
2023-04-11 13:27 dpdklab
2023-04-11 13:27 dpdklab
2023-04-11 13:18 dpdklab
2023-04-11 12:32 dpdklab
2023-04-11 12:29 dpdklab
2023-04-11 12:16 dpdklab
2023-04-11 12:11 dpdklab
2023-04-11 12:06 dpdklab
2023-04-11 12:02 dpdklab
2023-04-11 11:57 dpdklab
2023-04-11 11:52 dpdklab
2023-04-11 11:52 dpdklab
2023-04-11 11:50 dpdklab
2023-04-11 11:47 dpdklab
2023-04-11 11:46 dpdklab
2023-04-11 11:45 dpdklab
2023-04-11 11:39 dpdklab
2023-04-11 11:34 dpdklab
2023-04-11 11:33 dpdklab
2023-04-11 11:32 dpdklab
2023-04-11 11:22 dpdklab
2023-04-11 11:22 dpdklab
2023-04-11 11:18 dpdklab
2023-04-11 11:12 dpdklab
2023-04-11 11:01 dpdklab
2023-04-11 10:59 dpdklab
2023-04-11 10:55 dpdklab
2023-04-11 10:48 dpdklab
2023-04-11 10:41 dpdklab
2023-04-11 10:40 dpdklab
2023-04-11 10:40 dpdklab
2023-04-11 10:39 dpdklab
2023-04-11 10:39 dpdklab
2023-04-11 10:39 dpdklab
2023-04-11 10:33 dpdklab
2023-04-11 10:15 dpdklab
2023-04-11 10:12 dpdklab
2023-04-11 10:04 dpdklab
2023-04-11 9:59 dpdklab
2023-04-11 9:59 dpdklab
2023-04-11 9:58 dpdklab
2023-04-11 9:55 dpdklab
2023-04-11 9:52 dpdklab
2023-04-11 9:52 dpdklab
2023-04-11 9:50 dpdklab
[not found] <20230411075528.1125799-6-asekhar@marvell.com>
2023-04-11 7:47 ` |SUCCESS| pw125901-125905 [PATCH 5/5] " qemudev
2023-04-11 7:51 ` 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=20230411113141.14E5A60092@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).