From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] d2cfa0c7280051e7e6a385c0c8fa57f7b74f9ea0
Date: Mon, 24 Jul 2023 18:17:39 -0700 (PDT) [thread overview]
Message-ID: <64bf22b3.630a0220.8376e.2767SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
d2cfa0c7280051e7e6a385c0c8fa57f7b74f9ea0 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| RHEL 7 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| openSUSE Leap 15 | 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)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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/tarballs/25589/
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-25 1:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 1:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 16:54 dpdklab
2023-07-25 3:45 dpdklab
2023-07-25 2:57 dpdklab
2023-07-25 2:33 dpdklab
2023-07-25 2:32 dpdklab
2023-07-25 2:20 dpdklab
2023-07-25 1:57 dpdklab
2023-07-25 1:55 dpdklab
2023-07-25 1:48 dpdklab
2023-07-25 1:45 dpdklab
2023-07-25 1:41 dpdklab
2023-07-25 1:24 dpdklab
2023-07-25 1:24 dpdklab
2023-07-25 1:21 dpdklab
2023-07-25 1:19 dpdklab
2023-07-25 1:19 dpdklab
2023-07-25 1:15 dpdklab
2023-07-25 1:13 dpdklab
2023-07-25 1:13 dpdklab
2023-07-25 1:09 dpdklab
2023-07-25 1:07 dpdklab
2023-07-25 1:06 dpdklab
2023-07-25 1:05 dpdklab
2023-07-25 1:03 dpdklab
2023-07-25 1:01 dpdklab
2023-07-25 1:01 dpdklab
2023-07-25 1:01 dpdklab
2023-07-24 21:11 dpdklab
2023-07-24 19:23 dpdklab
2023-07-24 19:19 dpdklab
2023-07-24 19:18 dpdklab
2023-07-24 19:08 dpdklab
2023-07-24 19:03 dpdklab
2023-07-24 18:58 dpdklab
2023-07-24 18:56 dpdklab
2023-07-24 18:56 dpdklab
2023-07-24 18:49 dpdklab
2023-07-24 18:48 dpdklab
2023-07-24 18:35 dpdklab
2023-07-24 18:35 dpdklab
2023-07-24 18:34 dpdklab
2023-07-24 18:32 dpdklab
2023-07-24 18:31 dpdklab
2023-07-24 18:30 dpdklab
2023-07-24 18:29 dpdklab
2023-07-24 18:26 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=64bf22b3.630a0220.8376e.2767SMTPIN_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).