From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 12fcafcd62286933e6b167b14856d21f642efa5f
Date: Sat, 29 Jul 2023 18:07:42 -0700 (PDT) [thread overview]
Message-ID: <64c5b7de.620a0220.17f52.f812SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
12fcafcd62286933e6b167b14856d21f642efa5f --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25630/
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-30 1:07 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 1:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-01 2:18 dpdklab
2023-08-01 2:17 dpdklab
2023-07-31 21:56 dpdklab
2023-07-31 21:39 dpdklab
2023-07-31 21:16 dpdklab
2023-07-31 21:15 dpdklab
2023-07-31 21:12 dpdklab
2023-07-31 21:06 dpdklab
2023-07-31 21:03 dpdklab
2023-07-31 19:51 dpdklab
2023-07-31 17:44 dpdklab
2023-07-31 17:16 dpdklab
2023-07-31 16:48 dpdklab
2023-07-31 16:42 dpdklab
2023-07-31 16:42 dpdklab
2023-07-31 16:06 dpdklab
2023-07-31 16:03 dpdklab
2023-07-31 16:01 dpdklab
2023-07-31 15:59 dpdklab
2023-07-31 15:57 dpdklab
2023-07-31 15:55 dpdklab
2023-07-31 15:02 dpdklab
2023-07-31 15:02 dpdklab
2023-07-31 15:00 dpdklab
2023-07-31 14:21 dpdklab
2023-07-31 14:20 dpdklab
2023-07-31 14:11 dpdklab
2023-07-31 14:11 dpdklab
2023-07-31 13:58 dpdklab
2023-07-31 11:51 dpdklab
2023-07-31 11:45 dpdklab
2023-07-31 11:40 dpdklab
2023-07-31 11:37 dpdklab
2023-07-31 11:27 dpdklab
2023-07-31 11:26 dpdklab
2023-07-31 11:25 dpdklab
2023-07-31 11:23 dpdklab
2023-07-31 11:22 dpdklab
2023-07-31 11:21 dpdklab
2023-07-31 11:18 dpdklab
2023-07-31 6:49 dpdklab
2023-07-31 3:43 dpdklab
2023-07-31 2:25 dpdklab
2023-07-31 2:13 dpdklab
2023-07-31 2:10 dpdklab
2023-07-31 1:56 dpdklab
2023-07-31 1:56 dpdklab
2023-07-31 1:45 dpdklab
2023-07-31 1:41 dpdklab
2023-07-31 1:41 dpdklab
2023-07-31 1:39 dpdklab
2023-07-31 1:33 dpdklab
2023-07-31 1:30 dpdklab
2023-07-31 1:29 dpdklab
2023-07-31 1:28 dpdklab
2023-07-31 1:24 dpdklab
2023-07-31 1:21 dpdklab
2023-07-31 1:17 dpdklab
2023-07-31 1:16 dpdklab
2023-07-31 1:10 dpdklab
2023-07-31 1:09 dpdklab
2023-07-31 1:07 dpdklab
2023-07-31 1:05 dpdklab
2023-07-31 1:05 dpdklab
2023-07-31 1:03 dpdklab
2023-07-31 1:01 dpdklab
2023-07-31 1:00 dpdklab
2023-07-31 1:00 dpdklab
2023-07-31 1:00 dpdklab
2023-07-30 10:13 dpdklab
2023-07-30 3:49 dpdklab
2023-07-30 2:43 dpdklab
2023-07-30 2:17 dpdklab
2023-07-30 2:16 dpdklab
2023-07-30 1:55 dpdklab
2023-07-30 1:50 dpdklab
2023-07-30 1:45 dpdklab
2023-07-30 1:32 dpdklab
2023-07-30 1:26 dpdklab
2023-07-30 1:22 dpdklab
2023-07-30 1:20 dpdklab
2023-07-30 1:20 dpdklab
2023-07-30 1:18 dpdklab
2023-07-30 1:08 dpdklab
2023-07-30 1:07 dpdklab
2023-07-30 1:07 dpdklab
2023-07-30 1:07 dpdklab
2023-07-30 1:06 dpdklab
2023-07-30 1:06 dpdklab
2023-07-30 1:05 dpdklab
2023-07-29 22:04 dpdklab
2023-07-29 19:46 dpdklab
2023-07-29 19:35 dpdklab
2023-07-29 19:24 dpdklab
2023-07-29 19:07 dpdklab
2023-07-29 19:07 dpdklab
2023-07-29 19:01 dpdklab
2023-07-29 19:01 dpdklab
2023-07-29 19:01 dpdklab
2023-07-29 19:00 dpdklab
2023-07-29 18:59 dpdklab
2023-07-29 18:57 dpdklab
2023-07-29 18:56 dpdklab
2023-07-29 18:52 dpdklab
2023-07-29 18:51 dpdklab
2023-07-29 18:49 dpdklab
2023-07-29 18:48 dpdklab
2023-07-29 12:17 dpdklab
2023-07-29 3:45 dpdklab
2023-07-29 3:05 dpdklab
2023-07-29 2:44 dpdklab
2023-07-29 2:34 dpdklab
2023-07-29 2:17 dpdklab
2023-07-29 2:05 dpdklab
2023-07-29 1:56 dpdklab
2023-07-29 1:56 dpdklab
2023-07-29 1:51 dpdklab
2023-07-29 1:46 dpdklab
2023-07-29 1:34 dpdklab
2023-07-29 1:31 dpdklab
2023-07-29 1:29 dpdklab
2023-07-29 1:21 dpdklab
2023-07-29 1:17 dpdklab
2023-07-29 1:15 dpdklab
2023-07-29 1:11 dpdklab
2023-07-29 1:09 dpdklab
2023-07-29 1:07 dpdklab
2023-07-29 1:06 dpdklab
2023-07-29 1:06 dpdklab
2023-07-29 1:05 dpdklab
2023-07-29 1:04 dpdklab
2023-07-29 1:04 dpdklab
2023-07-29 1:04 dpdklab
2023-07-29 1:03 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=64c5b7de.620a0220.17f52.f812SMTPIN_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).