From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 025280d219fcfe79b558c2470c7fabc7014ef5a2
Date: Wed, 12 Jul 2023 14:31:32 -0700 (PDT) [thread overview]
Message-ID: <64af1bb4.0c0a0220.9f07b.0717SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-virtio
025280d219fcfe79b558c2470c7fabc7014ef5a2 --> functional testing pass
Test environment and result as below:
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25390/
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-12 21:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 21:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-13 11:33 dpdklab
2023-07-13 11:28 dpdklab
2023-07-13 11:23 dpdklab
2023-07-12 21:27 dpdklab
2023-07-12 19:23 dpdklab
2023-07-12 19:23 dpdklab
2023-07-08 22:27 dpdklab
2023-07-08 22:07 dpdklab
2023-07-07 6:17 dpdklab
2023-07-06 23:10 dpdklab
2023-07-06 22:48 dpdklab
2023-07-06 15:43 dpdklab
2023-07-06 15:40 dpdklab
2023-07-06 15:35 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=64af1bb4.0c0a0220.9f07b.0717SMTPIN_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).