From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 2125ed73e10ec028dd1b5fd6105aef80456e659e
Date: Thu, 08 Jun 2023 18:15:39 -0700 (PDT) [thread overview]
Message-ID: <64827d3b.050a0220.6a24b.8680SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
2125ed73e10ec028dd1b5fd6105aef80456e659e --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| RHEL 7 | PASS |
+-----------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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/24923/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-09 1:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 1:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-10 23:23 dpdklab
2023-06-10 10:53 dpdklab
2023-06-09 20:33 dpdklab
2023-06-09 20:27 dpdklab
2023-06-09 20:23 dpdklab
2023-06-09 20:13 dpdklab
2023-06-09 19:58 dpdklab
2023-06-09 16:19 dpdklab
2023-06-09 16:18 dpdklab
2023-06-09 14:36 dpdklab
2023-06-09 14:32 dpdklab
2023-06-09 14:22 dpdklab
2023-06-09 14:18 dpdklab
2023-06-09 14:01 dpdklab
2023-06-09 11:54 dpdklab
2023-06-09 11:52 dpdklab
2023-06-09 11:52 dpdklab
2023-06-09 11:47 dpdklab
2023-06-09 11:41 dpdklab
2023-06-09 11:36 dpdklab
2023-06-09 11:25 dpdklab
2023-06-09 11:24 dpdklab
2023-06-09 11:24 dpdklab
2023-06-09 11:19 dpdklab
2023-06-09 11:19 dpdklab
2023-06-09 8:36 dpdklab
2023-06-09 8:36 dpdklab
2023-06-09 3:47 dpdklab
2023-06-09 2:37 dpdklab
2023-06-09 2:30 dpdklab
2023-06-09 2:25 dpdklab
2023-06-09 1:57 dpdklab
2023-06-09 1:55 dpdklab
2023-06-09 1:51 dpdklab
2023-06-09 1:39 dpdklab
2023-06-09 1:32 dpdklab
2023-06-09 1:31 dpdklab
2023-06-09 1:22 dpdklab
2023-06-09 1:20 dpdklab
2023-06-09 1:10 dpdklab
2023-06-09 1:10 dpdklab
2023-06-09 1:05 dpdklab
2023-06-09 1:04 dpdklab
2023-06-09 1:04 dpdklab
2023-06-09 0:59 dpdklab
2023-06-09 0:58 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=64827d3b.050a0220.6a24b.8680SMTPIN_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).