From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 2ac57ed414af92f0c30a799e1824fd47f86a94b0
Date: Fri, 05 Apr 2024 05:06:21 -0700 (PDT) [thread overview]
Message-ID: <660fe93d.170a0220.149c9.e0b4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net-intel
2ac57ed414af92f0c30a799e1824fd47f86a94b0 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
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: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28729/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-04-05 12:06 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 12:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-05 12:42 dpdklab
2024-04-05 12:40 dpdklab
2024-04-05 12:32 dpdklab
2024-04-05 12:27 dpdklab
2024-04-05 12:26 dpdklab
2024-04-05 12:25 dpdklab
2024-04-05 12:24 dpdklab
2024-04-05 12:22 dpdklab
2024-04-05 12:20 dpdklab
2024-04-05 12:10 dpdklab
2024-04-05 12:08 dpdklab
2024-04-05 12:07 dpdklab
2024-04-05 12:05 dpdklab
2024-04-05 12:05 dpdklab
2024-04-05 12:04 dpdklab
2024-04-05 12:04 dpdklab
2024-04-05 12:02 dpdklab
2024-04-05 11:35 dpdklab
2024-04-05 11:35 dpdklab
2024-04-05 11:34 dpdklab
2024-04-05 11:33 dpdklab
2024-04-05 11:29 dpdklab
2024-04-05 11:29 dpdklab
2024-04-05 11:29 dpdklab
2024-04-05 11:29 dpdklab
2024-04-05 11:29 dpdklab
2024-04-05 11:29 dpdklab
2024-04-05 11:28 dpdklab
2024-04-05 11:28 dpdklab
2024-04-05 11:28 dpdklab
2024-04-05 11:28 dpdklab
2024-04-05 11:28 dpdklab
2024-04-05 11:28 dpdklab
2024-04-05 11:26 dpdklab
2024-04-05 11:26 dpdklab
2024-04-05 11:26 dpdklab
2024-04-05 11:26 dpdklab
2024-04-05 11:25 dpdklab
2024-04-05 11:24 dpdklab
2024-04-05 11:24 dpdklab
2024-04-05 11:24 dpdklab
2024-04-05 11:23 dpdklab
2024-04-05 11:22 dpdklab
2024-04-05 11:22 dpdklab
2024-04-05 11:22 dpdklab
2024-04-05 11:22 dpdklab
2024-04-05 11:22 dpdklab
2024-04-05 11:21 dpdklab
2024-04-05 11:19 dpdklab
2024-04-05 11:19 dpdklab
2024-04-05 11:18 dpdklab
2024-04-05 11:18 dpdklab
2024-04-05 11:17 dpdklab
2024-04-05 11:17 dpdklab
2024-04-05 11:16 dpdklab
2024-04-05 11:16 dpdklab
2024-04-05 11:15 dpdklab
2024-04-05 11:15 dpdklab
2024-04-05 11:15 dpdklab
2024-04-05 11:14 dpdklab
2024-04-05 11:14 dpdklab
2024-04-05 11:14 dpdklab
2024-04-05 11:12 dpdklab
2024-04-05 11:12 dpdklab
2024-04-05 11:12 dpdklab
2024-04-05 11:11 dpdklab
2024-04-05 11:10 dpdklab
2024-04-05 11:10 dpdklab
2024-04-05 11:09 dpdklab
2024-04-05 11:09 dpdklab
2024-04-05 11:08 dpdklab
2024-04-05 11:08 dpdklab
2024-04-05 11:08 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=660fe93d.170a0220.149c9.e0b4SMTPIN_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).