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
Subject: |SUCCESS| [GIT MASTER] 3408b132b31906fe1ed28d6b2009b98202e1cff0
Date: Mon, 04 Mar 2024 15:31:05 -0800 (PST)	[thread overview]
Message-ID: <65e659b9.170a0220.57f6a.c2deSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net-intel

3408b132b31906fe1ed28d6b2009b98202e1cff0 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
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 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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-04 23:31 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 23:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-05  0:36 dpdklab
2024-03-05  0:03 dpdklab
2024-03-02 19:39 dpdklab
2024-03-02 19:31 dpdklab
2024-03-02 16:57 dpdklab
2024-03-02  3:23 dpdklab
2024-03-02  3:14 dpdklab
2024-03-02  1:16 dpdklab
2024-03-01 19:58 dpdklab
2024-03-01 17:55 dpdklab
2024-03-01 17:43 dpdklab
2024-03-01 17:33 dpdklab
2024-03-01 13:38 dpdklab
2024-03-01 12:27 dpdklab
2024-03-01 12:18 dpdklab
2024-03-01 12:15 dpdklab
2024-03-01 12:12 dpdklab
2024-03-01 12:12 dpdklab
2024-03-01 12:10 dpdklab
2024-03-01 12:10 dpdklab
2024-03-01 12:09 dpdklab
2024-03-01 12:08 dpdklab
2024-03-01 12:08 dpdklab
2024-03-01 12:08 dpdklab
2024-03-01 12:08 dpdklab
2024-03-01 12:08 dpdklab
2024-03-01 12:07 dpdklab
2024-03-01 12:07 dpdklab
2024-03-01 12:07 dpdklab
2024-03-01 12:07 dpdklab
2024-03-01 12:07 dpdklab
2024-03-01 12:07 dpdklab
2024-03-01 12:06 dpdklab
2024-03-01 12:06 dpdklab
2024-03-01 12:06 dpdklab
2024-03-01 12:06 dpdklab
2024-03-01 12:05 dpdklab
2024-03-01 12:05 dpdklab
2024-03-01 12:05 dpdklab
2024-03-01 12:05 dpdklab
2024-03-01 12:04 dpdklab
2024-03-01 12:04 dpdklab
2024-03-01 12:04 dpdklab
2024-03-01 12:04 dpdklab
2024-03-01 12:04 dpdklab
2024-03-01 12:03 dpdklab
2024-03-01 12:03 dpdklab
2024-03-01 12:03 dpdklab
2024-03-01 12:03 dpdklab
2024-03-01 12:02 dpdklab
2024-03-01 12:02 dpdklab
2024-03-01 12:01 dpdklab
2024-03-01 12:01 dpdklab
2024-03-01 12:01 dpdklab
2024-03-01 12:01 dpdklab
2024-03-01 12:01 dpdklab
2024-03-01 12:00 dpdklab
2024-03-01 12:00 dpdklab
2024-03-01 12:00 dpdklab
2024-03-01 11:59 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=65e659b9.170a0220.57f6a.c2deSMTPIN_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).