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| pw137099 [PATCH] [v9] net/bnx2x: fix warnings about rte_me
Date: Fri, 23 Feb 2024 15:41:38 -0800 (PST)	[thread overview]
Message-ID: <65d92d32.050a0220.6aef5.047aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Friday, February 23 2024 14:00:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e9c81b801b647b1e06bb9f0e6da99b49b28b5162

137099 --> 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-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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-23 23:41 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 23:41 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-24 10:10 dpdklab
2024-02-24  9:36 dpdklab
2024-02-24  9:26 dpdklab
2024-02-24  4:55 dpdklab
2024-02-24  2:25 dpdklab
2024-02-24  2:18 dpdklab
2024-02-24  2:15 dpdklab
2024-02-24  2:08 dpdklab
2024-02-24  2:06 dpdklab
2024-02-24  2:02 dpdklab
2024-02-24  1:58 dpdklab
2024-02-24  1:58 dpdklab
2024-02-24  1:57 dpdklab
2024-02-24  1:54 dpdklab
2024-02-24  1:38 dpdklab
2024-02-24  1:36 dpdklab
2024-02-24  1:35 dpdklab
2024-02-24  1:33 dpdklab
2024-02-24  1:33 dpdklab
2024-02-24  1:32 dpdklab
2024-02-24  1:31 dpdklab
2024-02-24  1:31 dpdklab
2024-02-24  1:21 dpdklab
2024-02-24  1:21 dpdklab
2024-02-24  1:21 dpdklab
2024-02-24  1:20 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:15 dpdklab
2024-02-24  1:11 dpdklab
2024-02-24  1:11 dpdklab
2024-02-24  1:05 dpdklab
2024-02-24  1:05 dpdklab
2024-02-24  1:05 dpdklab
2024-02-24  1:05 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:03 dpdklab
2024-02-24  0:55 dpdklab
2024-02-24  0:53 dpdklab
2024-02-24  0:53 dpdklab
2024-02-24  0:52 dpdklab
2024-02-24  0:39 dpdklab
2024-02-24  0:38 dpdklab
2024-02-24  0:37 dpdklab
2024-02-24  0:36 dpdklab
2024-02-24  0:36 dpdklab
2024-02-24  0:33 dpdklab
2024-02-24  0:29 dpdklab
2024-02-24  0:29 dpdklab
2024-02-24  0:26 dpdklab
2024-02-24  0:21 dpdklab
2024-02-24  0:21 dpdklab
2024-02-24  0:03 dpdklab
2024-02-24  0:02 dpdklab
2024-02-24  0:02 dpdklab
2024-02-23 23:48 dpdklab
2024-02-23 23:47 dpdklab
2024-02-23 23:46 dpdklab
2024-02-23 23:42 dpdklab
2024-02-23 23:42 dpdklab
2024-02-23 23:41 dpdklab
2024-02-23 23:40 dpdklab
2024-02-23 23:39 dpdklab
2024-02-23 23:39 dpdklab
2024-02-23 23:34 dpdklab
2024-02-23 23:32 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=65d92d32.050a0220.6aef5.047aSMTPIN_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).