From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 70b6941e4e22d67bc10495d1638234a7e974f582
Date: Wed, 09 Aug 2023 18:24:51 -0700 (PDT) [thread overview]
Message-ID: <64d43c63.050a0220.f733a.2470SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
70b6941e4e22d67bc10495d1638234a7e974f582 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
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
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 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/25750/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-10 1:24 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 1:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-12 0:11 dpdklab
2023-08-11 23:23 dpdklab
2023-08-11 22:30 dpdklab
2023-08-11 22:30 dpdklab
2023-08-11 22:29 dpdklab
2023-08-11 22:29 dpdklab
2023-08-11 22:29 dpdklab
2023-08-11 22:29 dpdklab
2023-08-11 22:28 dpdklab
2023-08-11 22:27 dpdklab
2023-08-11 22:26 dpdklab
2023-08-11 21:36 dpdklab
2023-08-11 21:20 dpdklab
2023-08-11 21:15 dpdklab
2023-08-11 21:10 dpdklab
2023-08-11 20:59 dpdklab
2023-08-11 10:02 dpdklab
2023-08-11 8:22 dpdklab
2023-08-11 7:57 dpdklab
2023-08-11 7:55 dpdklab
2023-08-11 7:53 dpdklab
2023-08-11 7:50 dpdklab
2023-08-11 7:48 dpdklab
2023-08-11 7:46 dpdklab
2023-08-11 7:42 dpdklab
2023-08-11 7:37 dpdklab
2023-08-11 7:33 dpdklab
2023-08-11 7:30 dpdklab
2023-08-11 6:41 dpdklab
2023-08-11 6:28 dpdklab
2023-08-11 5:36 dpdklab
2023-08-11 5:33 dpdklab
2023-08-11 5:31 dpdklab
2023-08-11 5:27 dpdklab
2023-08-11 5:25 dpdklab
2023-08-11 5:24 dpdklab
2023-08-11 5:23 dpdklab
2023-08-11 5:23 dpdklab
2023-08-11 5:15 dpdklab
2023-08-11 5:13 dpdklab
2023-08-11 5:12 dpdklab
2023-08-11 5:12 dpdklab
2023-08-11 5:10 dpdklab
2023-08-11 5:10 dpdklab
2023-08-11 5:09 dpdklab
2023-08-11 5:08 dpdklab
2023-08-11 5:07 dpdklab
2023-08-11 5:05 dpdklab
2023-08-11 5:05 dpdklab
2023-08-11 4:38 dpdklab
2023-08-11 2:11 dpdklab
2023-08-11 2:10 dpdklab
2023-08-11 2:07 dpdklab
2023-08-11 2:06 dpdklab
2023-08-11 2:06 dpdklab
2023-08-11 2:04 dpdklab
2023-08-11 2:03 dpdklab
2023-08-11 2:02 dpdklab
2023-08-10 2:27 dpdklab
2023-08-10 2:14 dpdklab
2023-08-10 2:03 dpdklab
2023-08-10 2:01 dpdklab
2023-08-10 2:00 dpdklab
2023-08-10 1:56 dpdklab
2023-08-10 1:39 dpdklab
2023-08-10 1:39 dpdklab
2023-08-10 1:39 dpdklab
2023-08-10 1:35 dpdklab
2023-08-10 1:20 dpdklab
2023-08-10 1:14 dpdklab
2023-08-10 1:11 dpdklab
2023-08-10 1:09 dpdklab
2023-08-10 1:07 dpdklab
2023-08-10 1:02 dpdklab
2023-08-10 0:59 dpdklab
2023-08-10 0:59 dpdklab
2023-08-09 9:22 dpdklab
2023-08-09 9:12 dpdklab
2023-08-09 9:07 dpdklab
2023-08-09 8:51 dpdklab
2023-08-09 8:46 dpdklab
2023-08-09 2:43 dpdklab
2023-08-09 2:17 dpdklab
2023-08-09 2:16 dpdklab
2023-08-09 2:13 dpdklab
2023-08-09 2:09 dpdklab
2023-08-09 2:09 dpdklab
2023-08-09 1:52 dpdklab
2023-08-09 1:37 dpdklab
2023-08-09 1:29 dpdklab
2023-08-09 1:25 dpdklab
2023-08-09 1:23 dpdklab
2023-08-09 1:22 dpdklab
2023-08-09 1:22 dpdklab
2023-08-09 1:20 dpdklab
2023-08-09 1:20 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=64d43c63.050a0220.f733a.2470SMTPIN_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).