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] a2a8cb4251308ce5ccbe391576fe6483c3adbc4c
Date: Tue, 14 Feb 2023 14:26:23 -0500 (EST)	[thread overview]
Message-ID: <20230214192623.24CC04AC@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

_Functional Testing PASS_

Branch: dpdk-next-net

a2a8cb4251308ce5ccbe391576fe6483c3adbc4c --> functional testing pass

Test environment and result as below:

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/23320/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-14 19:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 19:26 dpdklab [this message]
2023-02-14 19:32 dpdklab
2023-02-14 19:34 dpdklab
2023-02-14 19:37 dpdklab
2023-02-14 19:38 dpdklab
2023-02-14 19:50 dpdklab
2023-02-14 20:09 dpdklab
2023-02-14 20:13 dpdklab
2023-02-14 20:18 dpdklab
2023-02-14 20:19 dpdklab
2023-02-14 20:23 dpdklab
2023-02-14 20:27 dpdklab
2023-02-14 20:34 dpdklab
2023-02-14 20:41 dpdklab
2023-02-14 20:42 dpdklab
2023-02-14 20:43 dpdklab
2023-02-14 20:44 dpdklab
2023-02-14 20:45 dpdklab
2023-02-16 11:00 dpdklab
2023-02-18  2:07 dpdklab
2023-02-23 21:08 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=20230214192623.24CC04AC@noxus.dpdklab.iol.unh.edu \
    --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).