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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125038-125049 [PATCH] [v6, 12/12] app/mldev: add documentation for mldev test cases
Date: Sat, 11 Mar 2023 18:39:27 +0000 (UTC)	[thread overview]
Message-ID: <20230311183927.F13166011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125049

_Functional Testing PASS_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Saturday, March 11 2023 15:09:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b15d75b2872efce397d827dac78692a919358302

125038-125049 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 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


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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/patchsets/25695/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-11 18:39 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 18:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-13 18:06 dpdklab
2023-03-13 16:42 dpdklab
2023-03-13  1:27 dpdklab
2023-03-13  1:27 dpdklab
2023-03-13  1:22 dpdklab
2023-03-13  1:14 dpdklab
2023-03-13  1:13 dpdklab
2023-03-13  1:12 dpdklab
2023-03-13  1:10 dpdklab
2023-03-13  1:01 dpdklab
2023-03-13  0:43 dpdklab
2023-03-13  0:37 dpdklab
2023-03-13  0:37 dpdklab
2023-03-13  0:37 dpdklab
2023-03-13  0:36 dpdklab
2023-03-13  0:34 dpdklab
2023-03-13  0:25 dpdklab
2023-03-13  0:24 dpdklab
2023-03-12 23:48 dpdklab
2023-03-12 23:46 dpdklab
2023-03-12 23:45 dpdklab
2023-03-12 23:41 dpdklab
2023-03-12 23:37 dpdklab
2023-03-12 23:36 dpdklab
2023-03-12 23:30 dpdklab
2023-03-12 23:26 dpdklab
2023-03-12 23:24 dpdklab
2023-03-12 23:20 dpdklab
2023-03-12 23:19 dpdklab
2023-03-12 23:12 dpdklab
2023-03-12 14:08 dpdklab
2023-03-12 13:14 dpdklab
2023-03-12 13:11 dpdklab
2023-03-12 12:55 dpdklab
2023-03-11 19:40 dpdklab
2023-03-11 18:54 dpdklab
2023-03-11 18:49 dpdklab
2023-03-11 18:44 dpdklab
2023-03-11 18:42 dpdklab
2023-03-11 18:41 dpdklab
2023-03-11 18:39 dpdklab
2023-03-11 18:36 dpdklab
2023-03-11 18:35 dpdklab
2023-03-11 18:35 dpdklab
2023-03-11 18:33 dpdklab
2023-03-11 18:32 dpdklab
2023-03-11 18:28 dpdklab
2023-03-11 18:22 dpdklab
2023-03-11 18:11 dpdklab
2023-03-11 18:07 dpdklab
2023-03-11 18:02 dpdklab
2023-03-11 18:01 dpdklab
2023-03-11 17:59 dpdklab
2023-03-11 17:59 dpdklab
2023-03-11 17:57 dpdklab
2023-03-11 17:54 dpdklab
2023-03-11 17:52 dpdklab
2023-03-11 17:52 dpdklab
2023-03-11 17:51 dpdklab
2023-03-11 17:50 dpdklab
2023-03-11 17:40 dpdklab
     [not found] <20230311150905.26824-13-syalavarthi@marvell.com>
2023-03-11 15:02 ` |SUCCESS| pw125038-125049 [PATCH v6 " qemudev
2023-03-11 15:06 ` qemudev

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=20230311183927.F13166011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).