From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] a399d7b5a994e335c446d4b15d7622d71dd8848c
Date: Fri, 19 May 2023 18:12:14 -0700 (PDT) [thread overview]
Message-ID: <64681e6e.630a0220.1dea1.2460SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
a399d7b5a994e335c446d4b15d7622d71dd8848c --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24649/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-20 1:12 UTC|newest]
Thread overview: 276+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 1:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-23 8:40 dpdklab
2023-05-23 8:39 dpdklab
2023-05-23 7:46 dpdklab
2023-05-23 7:42 dpdklab
2023-05-23 7:31 dpdklab
2023-05-23 7:11 dpdklab
2023-05-23 7:11 dpdklab
2023-05-23 5:41 dpdklab
2023-05-23 4:19 dpdklab
2023-05-23 4:06 dpdklab
2023-05-23 4:02 dpdklab
2023-05-23 3:30 dpdklab
2023-05-23 3:22 dpdklab
2023-05-23 3:19 dpdklab
2023-05-23 3:18 dpdklab
2023-05-23 3:15 dpdklab
2023-05-23 3:05 dpdklab
2023-05-23 3:03 dpdklab
2023-05-23 2:58 dpdklab
2023-05-23 2:50 dpdklab
2023-05-23 2:28 dpdklab
2023-05-23 1:53 dpdklab
2023-05-23 1:43 dpdklab
2023-05-23 1:39 dpdklab
2023-05-23 1:34 dpdklab
2023-05-23 1:18 dpdklab
2023-05-23 1:14 dpdklab
2023-05-23 1:12 dpdklab
2023-05-23 1:04 dpdklab
2023-05-23 1:04 dpdklab
2023-05-23 1:04 dpdklab
2023-05-23 1:03 dpdklab
2023-05-23 1:02 dpdklab
2023-05-23 1:01 dpdklab
2023-05-23 1:00 dpdklab
2023-05-22 19:31 dpdklab
2023-05-22 19:24 dpdklab
2023-05-22 17:57 dpdklab
2023-05-22 17:47 dpdklab
2023-05-22 17:41 dpdklab
2023-05-22 17:41 dpdklab
2023-05-22 17:28 dpdklab
2023-05-22 17:28 dpdklab
2023-05-22 17:23 dpdklab
2023-05-22 17:22 dpdklab
2023-05-22 17:06 dpdklab
2023-05-22 17:04 dpdklab
2023-05-22 17:03 dpdklab
2023-05-22 16:45 dpdklab
2023-05-22 16:44 dpdklab
2023-05-22 16:37 dpdklab
2023-05-22 16:37 dpdklab
2023-05-22 16:35 dpdklab
2023-05-22 16:33 dpdklab
2023-05-22 16:29 dpdklab
2023-05-22 16:25 dpdklab
2023-05-22 16:20 dpdklab
2023-05-22 16:17 dpdklab
2023-05-22 16:16 dpdklab
2023-05-22 16:09 dpdklab
2023-05-22 16:00 dpdklab
2023-05-22 15:56 dpdklab
2023-05-22 15:55 dpdklab
2023-05-22 15:55 dpdklab
2023-05-22 15:54 dpdklab
2023-05-22 15:54 dpdklab
2023-05-22 15:53 dpdklab
2023-05-22 15:53 dpdklab
2023-05-22 15:53 dpdklab
2023-05-22 15:43 dpdklab
2023-05-22 15:43 dpdklab
2023-05-22 15:42 dpdklab
2023-05-22 15:35 dpdklab
2023-05-22 15:33 dpdklab
2023-05-22 2:40 dpdklab
2023-05-22 2:31 dpdklab
2023-05-22 2:30 dpdklab
2023-05-22 2:18 dpdklab
2023-05-22 2:09 dpdklab
2023-05-22 2:07 dpdklab
2023-05-22 2:07 dpdklab
2023-05-22 1:58 dpdklab
2023-05-22 1:50 dpdklab
2023-05-22 1:43 dpdklab
2023-05-22 1:38 dpdklab
2023-05-22 1:36 dpdklab
2023-05-22 1:34 dpdklab
2023-05-22 1:32 dpdklab
2023-05-22 1:28 dpdklab
2023-05-22 1:24 dpdklab
2023-05-22 1:22 dpdklab
2023-05-22 1:18 dpdklab
2023-05-22 1:18 dpdklab
2023-05-22 1:14 dpdklab
2023-05-22 1:12 dpdklab
2023-05-22 1:10 dpdklab
2023-05-22 1:09 dpdklab
2023-05-22 1:03 dpdklab
2023-05-22 1:03 dpdklab
2023-05-22 1:02 dpdklab
2023-05-22 1:02 dpdklab
2023-05-22 0:58 dpdklab
2023-05-22 0:56 dpdklab
2023-05-22 0:54 dpdklab
2023-05-21 2:50 dpdklab
2023-05-21 2:26 dpdklab
2023-05-21 2:17 dpdklab
2023-05-21 2:16 dpdklab
2023-05-21 2:12 dpdklab
2023-05-21 2:06 dpdklab
2023-05-21 2:03 dpdklab
2023-05-21 1:44 dpdklab
2023-05-21 1:42 dpdklab
2023-05-21 1:37 dpdklab
2023-05-21 1:35 dpdklab
2023-05-21 1:31 dpdklab
2023-05-21 1:29 dpdklab
2023-05-21 1:29 dpdklab
2023-05-21 1:27 dpdklab
2023-05-21 1:26 dpdklab
2023-05-21 1:22 dpdklab
2023-05-21 1:13 dpdklab
2023-05-21 1:10 dpdklab
2023-05-21 1:09 dpdklab
2023-05-21 1:08 dpdklab
2023-05-21 1:04 dpdklab
2023-05-21 1:04 dpdklab
2023-05-21 1:04 dpdklab
2023-05-21 1:04 dpdklab
2023-05-21 1:03 dpdklab
2023-05-21 0:56 dpdklab
2023-05-21 0:54 dpdklab
2023-05-20 7:04 dpdklab
2023-05-20 7:03 dpdklab
2023-05-20 2:28 dpdklab
2023-05-20 2:23 dpdklab
2023-05-20 2:21 dpdklab
2023-05-20 2:10 dpdklab
2023-05-20 1:54 dpdklab
2023-05-20 1:52 dpdklab
2023-05-20 1:46 dpdklab
2023-05-20 1:39 dpdklab
2023-05-20 1:38 dpdklab
2023-05-20 1:36 dpdklab
2023-05-20 1:35 dpdklab
2023-05-20 1:33 dpdklab
2023-05-20 1:29 dpdklab
2023-05-20 1:29 dpdklab
2023-05-20 1:26 dpdklab
2023-05-20 1:24 dpdklab
2023-05-20 1:24 dpdklab
2023-05-20 1:20 dpdklab
2023-05-20 1:11 dpdklab
2023-05-20 1:05 dpdklab
2023-05-20 1:05 dpdklab
2023-05-20 1:04 dpdklab
2023-05-20 1:03 dpdklab
2023-05-20 1:03 dpdklab
2023-05-20 0:57 dpdklab
2023-05-20 0:56 dpdklab
2023-05-19 22:21 dpdklab
2023-05-19 22:21 dpdklab
2023-05-19 16:16 dpdklab
2023-05-19 15:46 dpdklab
2023-05-19 4:20 dpdklab
2023-05-19 4:19 dpdklab
2023-05-19 4:07 dpdklab
2023-05-19 4:04 dpdklab
2023-05-19 3:59 dpdklab
2023-05-19 3:58 dpdklab
2023-05-19 3:57 dpdklab
2023-05-19 3:55 dpdklab
2023-05-19 3:52 dpdklab
2023-05-19 3:50 dpdklab
2023-05-19 3:45 dpdklab
2023-05-19 3:40 dpdklab
2023-05-19 3:39 dpdklab
2023-05-19 3:36 dpdklab
2023-05-19 3:25 dpdklab
2023-05-19 3:20 dpdklab
2023-05-19 3:10 dpdklab
2023-05-19 2:53 dpdklab
2023-05-19 2:07 dpdklab
2023-05-19 1:56 dpdklab
2023-05-19 1:32 dpdklab
2023-05-19 1:20 dpdklab
2023-05-19 1:13 dpdklab
2023-05-19 1:08 dpdklab
2023-05-19 1:07 dpdklab
2023-05-19 1:06 dpdklab
2023-05-18 12:55 dpdklab
2023-05-18 12:55 dpdklab
2023-05-18 5:10 dpdklab
2023-05-18 3:25 dpdklab
2023-05-18 3:22 dpdklab
2023-05-18 3:16 dpdklab
2023-05-18 3:12 dpdklab
2023-05-18 3:09 dpdklab
2023-05-18 3:05 dpdklab
2023-05-18 3:05 dpdklab
2023-05-18 3:04 dpdklab
2023-05-18 2:58 dpdklab
2023-05-18 2:42 dpdklab
2023-05-18 2:37 dpdklab
2023-05-18 2:33 dpdklab
2023-05-18 2:24 dpdklab
2023-05-18 2:21 dpdklab
2023-05-18 2:19 dpdklab
2023-05-18 2:16 dpdklab
2023-05-18 2:10 dpdklab
2023-05-18 2:00 dpdklab
2023-05-18 1:59 dpdklab
2023-05-18 1:40 dpdklab
2023-05-18 1:29 dpdklab
2023-05-18 1:20 dpdklab
2023-05-18 1:14 dpdklab
2023-05-18 1:13 dpdklab
2023-05-18 1:11 dpdklab
2023-05-18 1:07 dpdklab
2023-05-17 4:48 dpdklab
2023-05-17 4:43 dpdklab
2023-05-17 4:38 dpdklab
2023-05-17 4:34 dpdklab
2023-05-17 4:25 dpdklab
2023-05-17 2:18 dpdklab
2023-05-17 2:18 dpdklab
2023-05-17 2:18 dpdklab
2023-05-17 2:13 dpdklab
2023-05-17 2:10 dpdklab
2023-05-17 2:06 dpdklab
2023-05-17 1:40 dpdklab
2023-05-17 1:39 dpdklab
2023-05-17 1:39 dpdklab
2023-05-17 1:37 dpdklab
2023-05-17 1:30 dpdklab
2023-05-17 1:28 dpdklab
2023-05-17 1:28 dpdklab
2023-05-17 1:23 dpdklab
2023-05-17 1:14 dpdklab
2023-05-17 1:10 dpdklab
2023-05-17 1:06 dpdklab
2023-05-17 1:04 dpdklab
2023-05-17 1:04 dpdklab
2023-05-17 1:03 dpdklab
2023-05-17 1:03 dpdklab
2023-05-17 1:02 dpdklab
2023-05-17 0:56 dpdklab
2023-05-16 15:11 dpdklab
2023-05-16 15:02 dpdklab
2023-05-16 14:45 dpdklab
2023-05-16 14:40 dpdklab
2023-05-16 14:35 dpdklab
2023-05-16 2:21 dpdklab
2023-05-16 2:20 dpdklab
2023-05-16 2:12 dpdklab
2023-05-16 2:09 dpdklab
2023-05-16 2:09 dpdklab
2023-05-16 2:00 dpdklab
2023-05-16 1:53 dpdklab
2023-05-16 1:46 dpdklab
2023-05-16 1:40 dpdklab
2023-05-16 1:33 dpdklab
2023-05-16 1:30 dpdklab
2023-05-16 1:28 dpdklab
2023-05-16 1:26 dpdklab
2023-05-16 1:22 dpdklab
2023-05-16 1:17 dpdklab
2023-05-16 1:11 dpdklab
2023-05-16 1:10 dpdklab
2023-05-16 1:10 dpdklab
2023-05-16 1:03 dpdklab
2023-05-16 1:02 dpdklab
2023-05-16 1:02 dpdklab
2023-05-16 0:58 dpdklab
2023-05-16 0:56 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=64681e6e.630a0220.1dea1.2460SMTPIN_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).