From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] a64a4564705d18d20d20cfa16c79e795b7bf0f1e
Date: Tue, 04 Jul 2023 17:59:54 -0700 (PDT) [thread overview]
Message-ID: <64a4c08a.250a0220.712a0.7d99SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
a64a4564705d18d20d20cfa16c79e795b7bf0f1e --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| RHEL 7 | PASS |
+-----------------+----------+
| RHEL8 | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
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)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25318/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-05 0:59 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 0:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-15 2:56 dpdklab
2023-07-15 2:55 dpdklab
2023-07-12 6:47 dpdklab
2023-07-12 6:02 dpdklab
2023-07-12 2:02 dpdklab
2023-07-12 0:57 dpdklab
2023-07-11 23:04 dpdklab
2023-07-11 21:37 dpdklab
2023-07-10 21:48 dpdklab
2023-07-08 2:04 dpdklab
2023-07-08 1:44 dpdklab
2023-07-06 19:13 dpdklab
2023-07-06 18:07 dpdklab
2023-07-06 9:16 dpdklab
2023-07-06 8:01 dpdklab
2023-07-06 6:59 dpdklab
2023-07-06 3:47 dpdklab
2023-07-06 3:35 dpdklab
2023-07-06 3:30 dpdklab
2023-07-06 3:26 dpdklab
2023-07-06 3:24 dpdklab
2023-07-06 3:23 dpdklab
2023-07-06 3:21 dpdklab
2023-07-06 3:17 dpdklab
2023-07-06 3:16 dpdklab
2023-07-06 3:16 dpdklab
2023-07-06 3:16 dpdklab
2023-07-06 2:21 dpdklab
2023-07-06 2:16 dpdklab
2023-07-06 2:15 dpdklab
2023-07-05 1:56 dpdklab
2023-07-05 1:50 dpdklab
2023-07-05 1:50 dpdklab
2023-07-05 1:49 dpdklab
2023-07-05 1:46 dpdklab
2023-07-05 1:43 dpdklab
2023-07-05 1:42 dpdklab
2023-07-05 1:36 dpdklab
2023-07-05 1:29 dpdklab
2023-07-05 1:25 dpdklab
2023-07-05 1:20 dpdklab
2023-07-05 1:17 dpdklab
2023-07-05 1:12 dpdklab
2023-07-05 1:05 dpdklab
2023-07-05 1:04 dpdklab
2023-07-05 1:04 dpdklab
2023-07-05 1:04 dpdklab
2023-07-05 1:02 dpdklab
2023-07-05 1:02 dpdklab
2023-07-05 1:01 dpdklab
2023-07-05 1:01 dpdklab
2023-07-05 0:59 dpdklab
2023-07-05 0:59 dpdklab
2023-07-05 0:56 dpdklab
2023-07-05 0:56 dpdklab
2023-07-05 0:55 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=64a4c08a.250a0220.712a0.7d99SMTPIN_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).