From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 72206323a5dd3182b13f61b25a64abdddfee595c
Date: Fri, 22 Jul 2022 08:05:09 -0400 (EDT) [thread overview]
Message-ID: <20220722120509.B63766D34A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
_Functional Testing PASS_
Branch: dpdk-next-eventdev
72206323a5dd3182b13f61b25a64abdddfee595c --> 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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20821/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-07-22 12:05 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 12:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-23 17:03 dpdklab
2022-08-23 17:02 dpdklab
2022-08-23 17:00 dpdklab
2022-08-23 16:52 dpdklab
2022-08-23 16:50 dpdklab
2022-08-23 16:46 dpdklab
2022-08-23 16:44 dpdklab
2022-08-23 16:44 dpdklab
2022-08-23 16:44 dpdklab
2022-08-23 16:40 dpdklab
2022-08-12 20:15 dpdklab
2022-08-12 19:40 dpdklab
2022-08-12 19:36 dpdklab
2022-08-12 19:36 dpdklab
2022-08-12 19:28 dpdklab
2022-08-12 19:24 dpdklab
2022-08-12 19:22 dpdklab
2022-08-12 19:16 dpdklab
2022-08-11 19:22 dpdklab
2022-08-11 18:52 dpdklab
2022-08-11 18:50 dpdklab
2022-08-11 18:48 dpdklab
2022-08-11 18:37 dpdklab
2022-08-11 18:36 dpdklab
2022-08-11 18:33 dpdklab
2022-08-11 18:27 dpdklab
2022-08-01 16:50 dpdklab
2022-08-01 16:43 dpdklab
2022-08-01 16:39 dpdklab
2022-08-01 16:38 dpdklab
2022-08-01 16:26 dpdklab
2022-08-01 16:25 dpdklab
2022-08-01 16:24 dpdklab
2022-08-01 16:21 dpdklab
2022-08-01 16:21 dpdklab
2022-07-26 19:14 dpdklab
2022-07-26 19:01 dpdklab
2022-07-26 18:58 dpdklab
2022-07-26 18:56 dpdklab
2022-07-26 18:51 dpdklab
2022-07-26 18:46 dpdklab
2022-07-26 18:35 dpdklab
2022-07-26 18:34 dpdklab
2022-07-26 18:29 dpdklab
2022-07-26 18:25 dpdklab
2022-07-26 18:14 dpdklab
2022-07-26 18:11 dpdklab
2022-07-26 18:07 dpdklab
2022-07-26 18:04 dpdklab
2022-07-26 17:55 dpdklab
2022-07-26 17:52 dpdklab
2022-07-26 17:47 dpdklab
2022-07-26 17:46 dpdklab
2022-07-26 17:45 dpdklab
2022-07-26 17:43 dpdklab
2022-07-26 17:39 dpdklab
2022-07-26 17:37 dpdklab
2022-07-26 17:36 dpdklab
2022-07-26 17:31 dpdklab
2022-07-26 17:30 dpdklab
2022-07-26 17:24 dpdklab
2022-07-26 17:24 dpdklab
2022-07-26 17:23 dpdklab
2022-07-26 17:22 dpdklab
2022-07-26 17:17 dpdklab
2022-07-22 12:48 dpdklab
2022-07-22 12:36 dpdklab
2022-07-22 12:21 dpdklab
2022-07-22 11:47 dpdklab
2022-07-22 11:44 dpdklab
2022-07-22 11:31 dpdklab
2022-07-22 11:28 dpdklab
2022-07-22 11:23 dpdklab
2022-07-22 11:20 dpdklab
2022-07-21 22:30 dpdklab
2022-07-21 22:27 dpdklab
2022-07-21 22:25 dpdklab
2022-07-21 22:20 dpdklab
2022-07-21 22:14 dpdklab
2022-07-21 22:08 dpdklab
2022-07-21 22:08 dpdklab
2022-07-21 22:07 dpdklab
2022-07-21 22:06 dpdklab
2022-07-21 22:01 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=20220722120509.B63766D34A@noxus.dpdklab.iol.unh.edu \
--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).