From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] ec932cb907b72291af28406d1621d6837771e10c
Date: Sun, 11 Feb 2024 18:06:12 -0800 (PST) [thread overview]
Message-ID: <65c97d14.a70a0220.25481.bf0aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
ec932cb907b72291af28406d1621d6837771e10c --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27972/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-12 2:06 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 2:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-12 3:27 dpdklab
2024-02-12 2:52 dpdklab
2024-02-12 2:50 dpdklab
2024-02-12 2:29 dpdklab
2024-02-12 2:24 dpdklab
2024-02-12 2:23 dpdklab
2024-02-12 2:16 dpdklab
2024-02-12 2:15 dpdklab
2024-02-12 2:14 dpdklab
2024-02-12 2:14 dpdklab
2024-02-12 2:13 dpdklab
2024-02-12 2:12 dpdklab
2024-02-12 2:11 dpdklab
2024-02-12 2:10 dpdklab
2024-02-12 2:10 dpdklab
2024-02-12 2:09 dpdklab
2024-02-12 2:08 dpdklab
2024-02-12 2:07 dpdklab
2024-02-12 2:07 dpdklab
2024-02-12 2:04 dpdklab
2024-02-12 2:04 dpdklab
2024-02-12 2:04 dpdklab
2024-02-12 2:03 dpdklab
2024-02-12 2:03 dpdklab
2024-02-12 2:03 dpdklab
2024-02-12 2:03 dpdklab
2024-02-12 2:03 dpdklab
2024-02-12 2:03 dpdklab
2024-02-12 2:02 dpdklab
2024-02-12 2:02 dpdklab
2024-02-12 2:02 dpdklab
2024-02-12 2:02 dpdklab
2024-02-12 2:02 dpdklab
2024-02-12 2:01 dpdklab
2024-02-12 2:00 dpdklab
2024-02-12 2:00 dpdklab
2024-02-12 1:59 dpdklab
2024-02-12 1:59 dpdklab
2024-02-12 1:58 dpdklab
2024-02-12 1:58 dpdklab
2024-02-12 1:58 dpdklab
2024-02-12 1:58 dpdklab
2024-02-12 1:57 dpdklab
2024-02-12 1:57 dpdklab
2024-02-12 1:56 dpdklab
2024-02-12 1:55 dpdklab
2024-02-12 1:55 dpdklab
2024-02-12 1:55 dpdklab
2024-02-12 1:54 dpdklab
2024-02-12 1:53 dpdklab
2024-02-12 1:52 dpdklab
2024-02-12 1:52 dpdklab
2024-02-10 3:12 dpdklab
2024-02-10 2:51 dpdklab
2024-02-10 2:50 dpdklab
2024-02-10 2:23 dpdklab
2024-02-10 2:22 dpdklab
2024-02-10 2:21 dpdklab
2024-02-10 2:17 dpdklab
2024-02-10 2:17 dpdklab
2024-02-10 2:16 dpdklab
2024-02-10 2:16 dpdklab
2024-02-10 2:15 dpdklab
2024-02-10 2:15 dpdklab
2024-02-10 2:12 dpdklab
2024-02-10 2:11 dpdklab
2024-02-10 2:10 dpdklab
2024-02-10 2:10 dpdklab
2024-02-10 2:08 dpdklab
2024-02-10 2:07 dpdklab
2024-02-10 2:07 dpdklab
2024-02-10 2:06 dpdklab
2024-02-10 2:05 dpdklab
2024-02-10 2:05 dpdklab
2024-02-10 2:05 dpdklab
2024-02-10 2:04 dpdklab
2024-02-10 2:04 dpdklab
2024-02-10 2:04 dpdklab
2024-02-10 2:04 dpdklab
2024-02-10 2:04 dpdklab
2024-02-10 2:03 dpdklab
2024-02-10 2:03 dpdklab
2024-02-10 2:03 dpdklab
2024-02-10 2:03 dpdklab
2024-02-10 2:03 dpdklab
2024-02-10 2:03 dpdklab
2024-02-10 2:02 dpdklab
2024-02-10 2:02 dpdklab
2024-02-10 2:02 dpdklab
2024-02-10 2:01 dpdklab
2024-02-10 2:01 dpdklab
2024-02-10 2:01 dpdklab
2024-02-10 2:01 dpdklab
2024-02-10 2:00 dpdklab
2024-02-10 2:00 dpdklab
2024-02-10 2:00 dpdklab
2024-02-10 2:00 dpdklab
2024-02-10 1:59 dpdklab
2024-02-10 1:59 dpdklab
2024-02-10 1:59 dpdklab
2024-02-10 1:59 dpdklab
2024-02-10 1:59 dpdklab
2024-02-10 1:58 dpdklab
2024-02-10 1:58 dpdklab
2024-02-10 1:58 dpdklab
2024-02-10 1:58 dpdklab
2024-02-10 1:57 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=65c97d14.a70a0220.25481.bf0aSMTPIN_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).