From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] b0b0e2ecd7d8185d8d497881214cb1e906196323
Date: Fri, 03 Nov 2023 14:09:15 -0700 (PDT) [thread overview]
Message-ID: <6545617b.170a0220.f7564.4943SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
b0b0e2ecd7d8185d8d497881214cb1e906196323 --> 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
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 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/26818/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-03 21:09 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 21:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 2:04 dpdklab
2023-11-04 0:29 dpdklab
2023-11-03 23:30 dpdklab
2023-11-03 23:28 dpdklab
2023-11-03 23:06 dpdklab
2023-11-03 22:57 dpdklab
2023-11-03 22:56 dpdklab
2023-11-03 22:52 dpdklab
2023-11-03 22:52 dpdklab
2023-11-03 22:52 dpdklab
2023-11-03 22:33 dpdklab
2023-11-03 22:31 dpdklab
2023-11-03 22:28 dpdklab
2023-11-03 22:28 dpdklab
2023-11-03 22:26 dpdklab
2023-11-03 22:26 dpdklab
2023-11-03 22:25 dpdklab
2023-11-03 22:22 dpdklab
2023-11-03 22:19 dpdklab
2023-11-03 22:18 dpdklab
2023-11-03 22:18 dpdklab
2023-11-03 22:16 dpdklab
2023-11-03 22:16 dpdklab
2023-11-03 22:16 dpdklab
2023-11-03 22:16 dpdklab
2023-11-03 22:16 dpdklab
2023-11-03 22:16 dpdklab
2023-11-03 22:14 dpdklab
2023-11-03 22:14 dpdklab
2023-11-03 22:14 dpdklab
2023-11-03 22:13 dpdklab
2023-11-03 22:13 dpdklab
2023-11-03 22:13 dpdklab
2023-11-03 22:13 dpdklab
2023-11-03 22:12 dpdklab
2023-11-03 22:09 dpdklab
2023-11-03 22:08 dpdklab
2023-11-03 22:07 dpdklab
2023-11-03 21:52 dpdklab
2023-11-03 21:31 dpdklab
2023-11-03 21:31 dpdklab
2023-11-03 21:17 dpdklab
2023-11-03 20:50 dpdklab
2023-11-03 20:45 dpdklab
2023-11-03 20:45 dpdklab
2023-11-03 20:45 dpdklab
2023-11-03 20:44 dpdklab
2023-11-03 20:44 dpdklab
2023-11-03 20:44 dpdklab
2023-11-03 20:30 dpdklab
2023-11-03 20:26 dpdklab
2023-11-03 20:25 dpdklab
2023-11-03 20:25 dpdklab
2023-11-03 20:24 dpdklab
2023-11-03 20:18 dpdklab
2023-11-03 20:18 dpdklab
2023-11-03 20:18 dpdklab
2023-11-03 20:18 dpdklab
2023-11-03 20:17 dpdklab
2023-11-03 20:12 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=6545617b.170a0220.f7564.4943SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).