automatic DPDK test reports
 help / color / mirror / Atom feed
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] 20db7deeb5131e46e859e212b334e8bef88ae701
Date: Tue, 19 Mar 2024 12:57:57 -0700 (PDT)	[thread overview]
Message-ID: <65f9ee45.050a0220.d6bca.c8adSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net

20db7deeb5131e46e859e212b334e8bef88ae701 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
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.83+
Compiler: gcc 11.4.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/1


Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.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/1


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28513/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-03-19 19:57 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 19:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-19 19:31 dpdklab
2024-03-16  8:24 dpdklab
2024-03-16  8:23 dpdklab
2024-03-16  7:58 dpdklab
2024-03-16  7:44 dpdklab
2024-03-16  7:42 dpdklab
2024-03-16  7:41 dpdklab
2024-03-16  7:40 dpdklab
2024-03-16  7:39 dpdklab
2024-03-16  7:37 dpdklab
2024-03-16  7:37 dpdklab
2024-03-16  7:37 dpdklab
2024-03-16  7:35 dpdklab
2024-03-16  7:32 dpdklab
2024-03-16  7:31 dpdklab
2024-03-16  7:31 dpdklab
2024-03-16  7:31 dpdklab
2024-03-16  7:30 dpdklab
2024-03-16  7:29 dpdklab
2024-03-16  7:28 dpdklab
2024-03-16  7:26 dpdklab
2024-03-16  7:25 dpdklab
2024-03-16  7:24 dpdklab
2024-03-16  7:22 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:20 dpdklab
2024-03-16  7:16 dpdklab
2024-03-16  7:16 dpdklab
2024-03-16  7:16 dpdklab
2024-03-16  7:15 dpdklab
2024-03-16  7:15 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:14 dpdklab
2024-03-16  7:13 dpdklab
2024-03-16  7:13 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:12 dpdklab
2024-03-16  7:11 dpdklab
2024-03-16  7:11 dpdklab
2024-03-16  7:10 dpdklab
2024-03-16  7:10 dpdklab
2024-03-16  7:10 dpdklab
2024-03-16  7:09 dpdklab
2024-03-16  7:09 dpdklab
2024-03-16  7:08 dpdklab
2024-03-16  7:08 dpdklab
2024-03-16  7:08 dpdklab
2024-03-16  7:07 dpdklab
2024-03-16  7:06 dpdklab
2024-03-16  6:49 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=65f9ee45.050a0220.d6bca.c8adSMTPIN_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).