From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] aa96e66c9abca5fa1e6024f9ddd52ee4f2e05b12
Date: Wed, 19 Apr 2023 05:34:41 +0000 (UTC) [thread overview]
Message-ID: <20230419053441.E407E60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing PASS_
Branch: tags/v22.11
aa96e66c9abca5fa1e6024f9ddd52ee4f2e05b12 --> testing pass
Test environment and result as below:
+--------------+----------+
| Environment | abi_test |
+==============+==========+
| Ubuntu 22.04 | PASS |
+--------------+----------+
| RHEL 7 | PASS |
+--------------+----------+
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
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/tarballs/24329/
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-19 5:34 UTC|newest]
Thread overview: 180+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 5:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 5:56 dpdklab
2023-04-24 5:54 dpdklab
2023-04-24 5:30 dpdklab
2023-04-24 5:29 dpdklab
2023-04-24 5:20 dpdklab
2023-04-24 5:03 dpdklab
2023-04-24 5:03 dpdklab
2023-04-24 4:54 dpdklab
2023-04-24 4:53 dpdklab
2023-04-24 4:53 dpdklab
2023-04-24 4:53 dpdklab
2023-04-24 4:48 dpdklab
2023-04-24 4:46 dpdklab
2023-04-24 4:44 dpdklab
2023-04-24 4:41 dpdklab
2023-04-24 4:33 dpdklab
2023-04-24 4:33 dpdklab
2023-04-24 4:33 dpdklab
2023-04-24 4:25 dpdklab
2023-04-24 4:25 dpdklab
2023-04-24 4:24 dpdklab
2023-04-24 4:21 dpdklab
2023-04-24 4:20 dpdklab
2023-04-24 4:16 dpdklab
2023-04-24 4:15 dpdklab
2023-04-23 5:50 dpdklab
2023-04-23 5:33 dpdklab
2023-04-23 5:31 dpdklab
2023-04-23 5:31 dpdklab
2023-04-23 5:11 dpdklab
2023-04-23 5:00 dpdklab
2023-04-23 4:57 dpdklab
2023-04-23 4:57 dpdklab
2023-04-23 4:55 dpdklab
2023-04-23 4:54 dpdklab
2023-04-23 4:53 dpdklab
2023-04-23 4:53 dpdklab
2023-04-23 4:53 dpdklab
2023-04-23 4:53 dpdklab
2023-04-23 4:50 dpdklab
2023-04-23 4:46 dpdklab
2023-04-23 4:44 dpdklab
2023-04-23 4:41 dpdklab
2023-04-23 4:32 dpdklab
2023-04-23 4:32 dpdklab
2023-04-23 4:31 dpdklab
2023-04-23 4:29 dpdklab
2023-04-23 4:27 dpdklab
2023-04-23 4:27 dpdklab
2023-04-23 4:24 dpdklab
2023-04-23 4:24 dpdklab
2023-04-23 4:20 dpdklab
2023-04-23 4:18 dpdklab
2023-04-22 7:25 dpdklab
2023-04-22 7:24 dpdklab
2023-04-22 6:52 dpdklab
2023-04-22 5:48 dpdklab
2023-04-22 5:18 dpdklab
2023-04-22 5:16 dpdklab
2023-04-22 5:09 dpdklab
2023-04-22 5:07 dpdklab
2023-04-22 5:03 dpdklab
2023-04-22 5:03 dpdklab
2023-04-22 5:00 dpdklab
2023-04-22 4:58 dpdklab
2023-04-22 4:46 dpdklab
2023-04-22 4:42 dpdklab
2023-04-22 4:34 dpdklab
2023-04-22 4:33 dpdklab
2023-04-22 4:32 dpdklab
2023-04-22 4:28 dpdklab
2023-04-22 4:26 dpdklab
2023-04-22 4:26 dpdklab
2023-04-22 4:26 dpdklab
2023-04-22 4:22 dpdklab
2023-04-22 4:22 dpdklab
2023-04-22 4:20 dpdklab
2023-04-21 10:05 dpdklab
2023-04-21 9:40 dpdklab
2023-04-21 9:40 dpdklab
2023-04-21 6:33 dpdklab
2023-04-21 6:31 dpdklab
2023-04-21 6:18 dpdklab
2023-04-21 6:11 dpdklab
2023-04-21 6:08 dpdklab
2023-04-21 6:07 dpdklab
2023-04-21 6:07 dpdklab
2023-04-21 5:58 dpdklab
2023-04-21 5:35 dpdklab
2023-04-21 4:55 dpdklab
2023-04-21 4:43 dpdklab
2023-04-21 4:34 dpdklab
2023-04-21 4:33 dpdklab
2023-04-21 4:32 dpdklab
2023-04-21 4:30 dpdklab
2023-04-21 4:29 dpdklab
2023-04-21 4:29 dpdklab
2023-04-21 4:28 dpdklab
2023-04-21 4:22 dpdklab
2023-04-21 4:21 dpdklab
2023-04-21 4:15 dpdklab
2023-04-20 14:34 dpdklab
2023-04-20 14:33 dpdklab
2023-04-20 14:26 dpdklab
2023-04-20 14:02 dpdklab
2023-04-20 14:00 dpdklab
2023-04-20 13:59 dpdklab
2023-04-20 13:57 dpdklab
2023-04-20 13:56 dpdklab
2023-04-20 13:55 dpdklab
2023-04-20 13:53 dpdklab
2023-04-20 13:49 dpdklab
2023-04-20 6:01 dpdklab
2023-04-20 5:36 dpdklab
2023-04-20 5:28 dpdklab
2023-04-20 5:28 dpdklab
2023-04-20 5:28 dpdklab
2023-04-20 5:15 dpdklab
2023-04-20 5:12 dpdklab
2023-04-20 4:57 dpdklab
2023-04-20 4:57 dpdklab
2023-04-20 4:52 dpdklab
2023-04-20 4:51 dpdklab
2023-04-20 4:51 dpdklab
2023-04-20 4:50 dpdklab
2023-04-20 4:49 dpdklab
2023-04-20 4:46 dpdklab
2023-04-20 4:44 dpdklab
2023-04-20 4:41 dpdklab
2023-04-20 4:32 dpdklab
2023-04-20 4:32 dpdklab
2023-04-20 4:31 dpdklab
2023-04-20 4:28 dpdklab
2023-04-20 4:28 dpdklab
2023-04-20 4:26 dpdklab
2023-04-20 4:24 dpdklab
2023-04-20 4:21 dpdklab
2023-04-20 4:18 dpdklab
2023-04-20 4:16 dpdklab
2023-04-19 17:01 dpdklab
2023-04-19 11:56 dpdklab
2023-04-19 7:29 dpdklab
2023-04-19 7:29 dpdklab
2023-04-19 6:37 dpdklab
2023-04-19 6:11 dpdklab
2023-04-19 5:49 dpdklab
2023-04-19 5:48 dpdklab
2023-04-19 5:47 dpdklab
2023-04-19 5:46 dpdklab
2023-04-19 5:45 dpdklab
2023-04-19 5:42 dpdklab
2023-04-19 5:32 dpdklab
2023-04-19 5:05 dpdklab
2023-04-19 4:53 dpdklab
2023-04-19 4:46 dpdklab
2023-04-19 4:45 dpdklab
2023-04-19 4:42 dpdklab
2023-04-19 4:40 dpdklab
2023-04-19 4:39 dpdklab
2023-04-19 4:34 dpdklab
2023-04-19 4:33 dpdklab
2023-04-19 4:31 dpdklab
2023-04-19 4:29 dpdklab
2023-04-19 4:28 dpdklab
2023-04-19 2:09 dpdklab
2023-04-18 16:32 dpdklab
2023-04-18 15:40 dpdklab
2023-04-18 14:50 dpdklab
2023-04-18 14:42 dpdklab
2023-04-18 14:36 dpdklab
2023-04-18 14:31 dpdklab
2023-04-18 14:31 dpdklab
2023-04-18 14:31 dpdklab
2023-04-18 14:26 dpdklab
2023-04-18 14:18 dpdklab
2023-04-18 14:17 dpdklab
2023-04-18 14:14 dpdklab
2023-04-18 14:13 dpdklab
2023-04-18 14:11 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=20230419053441.E407E60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).