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| pw136678 [PATCH] [V2] net/memif: fix extra mbuf refcnt upd
Date: Tue, 13 Feb 2024 23:48:37 -0800 (PST)	[thread overview]
Message-ID: <65cc7055.0d0a0220.d035e.923cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Wednesday, February 14 2024 00:36:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4cf59bbc9edf5419a9f2644a132c9a96c071a4c8

136678 --> functional testing pass

Test environment and result as below:

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


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


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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29142/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-14  7:48 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  7:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14 10:02 dpdklab
2024-02-14 10:01 dpdklab
2024-02-14  9:26 dpdklab
2024-02-14  8:13 dpdklab
2024-02-14  7:17 dpdklab
2024-02-14  6:33 dpdklab
2024-02-14  5:26 dpdklab
2024-02-14  5:13 dpdklab
2024-02-14  5:00 dpdklab
2024-02-14  4:48 dpdklab
2024-02-14  4:45 dpdklab
2024-02-14  4:43 dpdklab
2024-02-14  4:42 dpdklab
2024-02-14  4:40 dpdklab
2024-02-14  4:40 dpdklab
2024-02-14  4:40 dpdklab
2024-02-14  4:38 dpdklab
2024-02-14  4:38 dpdklab
2024-02-14  4:38 dpdklab
2024-02-14  4:37 dpdklab
2024-02-14  4:37 dpdklab
2024-02-14  4:37 dpdklab
2024-02-14  4:37 dpdklab
2024-02-14  4:37 dpdklab
2024-02-14  4:36 dpdklab
2024-02-14  4:36 dpdklab
2024-02-14  4:36 dpdklab
2024-02-14  4:36 dpdklab
2024-02-14  4:36 dpdklab
2024-02-14  4:35 dpdklab
2024-02-14  4:35 dpdklab
2024-02-14  4:35 dpdklab
2024-02-14  4:34 dpdklab
2024-02-14  4:34 dpdklab
2024-02-14  4:34 dpdklab
2024-02-14  4:34 dpdklab
2024-02-14  4:33 dpdklab
2024-02-14  4:33 dpdklab
2024-02-14  4:33 dpdklab
2024-02-14  4:32 dpdklab
2024-02-14  4:32 dpdklab
2024-02-14  4:31 dpdklab
2024-02-14  4:30 dpdklab
2024-02-14  4:30 dpdklab
2024-02-14  4:28 dpdklab
2024-02-14  4:27 dpdklab
2024-02-14  4:26 dpdklab
2024-02-14  4:26 dpdklab
2024-02-14  4:25 dpdklab
2024-02-14  4:15 dpdklab
2024-02-14  4:14 dpdklab
2024-02-14  4:14 dpdklab
2024-02-14  4:14 dpdklab
2024-02-14  4:13 dpdklab
2024-02-14  4:05 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=65cc7055.0d0a0220.d035e.923cSMTPIN_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).