From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137194-137196 [PATCH] [v3,3/3] event/cnxk: support DMA e
Date: Mon, 26 Feb 2024 03:30:51 -0800 (PST) [thread overview]
Message-ID: <65dc766b.0d0a0220.6e2cd.3ab8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137196
_Testing PASS_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Monday, February 26 2024 09:43:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137194-137196 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Fedora 37 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29258/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-26 11:30 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 11:30 dpdklab [this message]
[not found] <20240226094334.3657250-3-amitprakashs@marvell.com>
2024-02-28 0:16 ` dpdklab
2024-02-28 0:30 ` dpdklab
2024-02-28 0:33 ` dpdklab
2024-02-28 0:58 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 14:57 dpdklab
2024-02-26 14:37 dpdklab
2024-02-26 14:13 dpdklab
2024-02-26 13:23 dpdklab
2024-02-26 13:19 dpdklab
2024-02-26 13:06 dpdklab
2024-02-26 13:00 dpdklab
2024-02-26 12:56 dpdklab
2024-02-26 12:56 dpdklab
2024-02-26 12:55 dpdklab
2024-02-26 12:55 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:50 dpdklab
2024-02-26 12:50 dpdklab
2024-02-26 12:49 dpdklab
2024-02-26 12:48 dpdklab
2024-02-26 12:48 dpdklab
2024-02-26 12:48 dpdklab
2024-02-26 12:48 dpdklab
2024-02-26 12:45 dpdklab
2024-02-26 12:44 dpdklab
2024-02-26 12:44 dpdklab
2024-02-26 12:43 dpdklab
2024-02-26 12:38 dpdklab
2024-02-26 12:36 dpdklab
2024-02-26 12:36 dpdklab
2024-02-26 12:33 dpdklab
2024-02-26 12:18 dpdklab
2024-02-26 12:18 dpdklab
2024-02-26 12:18 dpdklab
2024-02-26 12:17 dpdklab
2024-02-26 12:16 dpdklab
2024-02-26 12:15 dpdklab
2024-02-26 11:57 dpdklab
2024-02-26 11:55 dpdklab
2024-02-26 11:54 dpdklab
2024-02-26 11:52 dpdklab
2024-02-26 11:47 dpdklab
2024-02-26 11:46 dpdklab
2024-02-26 11:41 dpdklab
2024-02-26 11:38 dpdklab
2024-02-26 11:37 dpdklab
2024-02-26 11:33 dpdklab
2024-02-26 11:31 dpdklab
2024-02-26 11:31 dpdklab
2024-02-26 11:28 dpdklab
2024-02-26 11:24 dpdklab
2024-02-26 11:23 dpdklab
2024-02-26 11:21 dpdklab
2024-02-26 11:20 dpdklab
2024-02-26 11:20 dpdklab
2024-02-26 11:19 dpdklab
2024-02-26 11:18 dpdklab
2024-02-26 11:17 dpdklab
2024-02-26 11:17 dpdklab
2024-02-26 11:17 dpdklab
2024-02-26 11:15 dpdklab
2024-02-26 11:14 dpdklab
2024-02-26 11:07 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=65dc766b.0d0a0220.6e2cd.3ab8SMTPIN_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).