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| pw130115-130145 [PATCH] [31/31] net/cnxk: fixes for IPv6 h
Date: Sat, 12 Aug 2023 00:23:47 -0700 (PDT)	[thread overview]
Message-ID: <64d73383.810a0220.ce537.bb40SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Friday, August 11 2023 08:58:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130115-130145 --> 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


Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.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/patchsets/27297/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-12  7:23 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  7:23 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-13 22:24 dpdklab
2023-08-13 22:13 dpdklab
2023-08-13 22:12 dpdklab
2023-08-13 22:12 dpdklab
2023-08-13 22:09 dpdklab
2023-08-13 22:08 dpdklab
2023-08-13 22:06 dpdklab
2023-08-13 22:03 dpdklab
2023-08-13 22:01 dpdklab
2023-08-13 22:01 dpdklab
2023-08-13 21:59 dpdklab
2023-08-13 21:58 dpdklab
2023-08-13 20:13 dpdklab
2023-08-13 19:00 dpdklab
2023-08-12  8:06 dpdklab
2023-08-12  8:01 dpdklab
2023-08-12  7:44 dpdklab
2023-08-12  7:33 dpdklab
2023-08-12  7:29 dpdklab
2023-08-12  1:45 dpdklab
2023-08-12  1:39 dpdklab
2023-08-12  1:37 dpdklab
2023-08-12  1:34 dpdklab
2023-08-12  1:31 dpdklab
2023-08-12  0:16 dpdklab
2023-08-12  0:14 dpdklab
2023-08-11 23:07 dpdklab
2023-08-11 22:40 dpdklab
2023-08-11 16:36 dpdklab
2023-08-11 16:30 dpdklab
2023-08-11 16:26 dpdklab
2023-08-11 16:25 dpdklab
2023-08-11 16:24 dpdklab
2023-08-11 16:22 dpdklab
2023-08-11 16:05 dpdklab
2023-08-11 16:05 dpdklab
2023-08-11 16:04 dpdklab
2023-08-11 16:03 dpdklab
2023-08-11 16:02 dpdklab
2023-08-11 16:00 dpdklab
2023-08-11 15:57 dpdklab
2023-08-11 15:35 dpdklab
2023-08-11 15:34 dpdklab
2023-08-11 15:34 dpdklab
2023-08-11 15:33 dpdklab
2023-08-11 15:31 dpdklab
2023-08-11 15:05 dpdklab
2023-08-11 15:05 dpdklab
2023-08-11 14:59 dpdklab
2023-08-11 14:57 dpdklab
2023-08-11 14:57 dpdklab
2023-08-11 14:51 dpdklab
2023-08-11 14:44 dpdklab
2023-08-11 14:38 dpdklab
2023-08-11 14:35 dpdklab
2023-08-11 14:33 dpdklab
2023-08-11 14:25 dpdklab
2023-08-11 14:23 dpdklab
2023-08-11 14:22 dpdklab
2023-08-11 14:22 dpdklab
2023-08-11 14:22 dpdklab
2023-08-11 14:21 dpdklab
2023-08-11 14:19 dpdklab
2023-08-11 14:19 dpdklab
2023-08-11 14:18 dpdklab
2023-08-11 14:18 dpdklab
2023-08-11 14:17 dpdklab
2023-08-11 14:16 dpdklab
2023-08-11 14:13 dpdklab
2023-08-11 14:12 dpdklab
2023-08-11 14:11 dpdklab
2023-08-11 14:08 dpdklab
2023-08-11 14:07 dpdklab
2023-08-11 13: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=64d73383.810a0220.ce537.bb40SMTPIN_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).