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| pw138166 [PATCH] net/bnx2x: fix indentation
Date: Mon, 11 Mar 2024 16:08:17 -0700 (PDT)	[thread overview]
Message-ID: <65ef8ee1.0d0a0220.79caf.7e25SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240311163912.11229-1-stephen@networkplumber.org>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138166

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, March 11 2024 16:39:12 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138166 --> 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 Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-11 23:08 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240311163912.11229-1-stephen@networkplumber.org>
2024-03-11 16:23 ` qemudev
2024-03-11 16:27 ` qemudev
2024-03-11 16:47 ` |WARNING| " checkpatch
2024-03-11 17:32 ` |SUCCESS| " dpdklab
2024-03-11 17:33 ` dpdklab
2024-03-11 17:33 ` dpdklab
2024-03-11 17:33 ` dpdklab
2024-03-11 17:34 ` dpdklab
2024-03-11 17:34 ` dpdklab
2024-03-11 17:38 ` dpdklab
2024-03-11 17:38 ` dpdklab
2024-03-11 17:39 ` dpdklab
2024-03-11 17:39 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:41 ` dpdklab
2024-03-11 17:41 ` dpdklab
2024-03-11 17:41 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` 0-day Robot
2024-03-11 17:43 ` dpdklab
2024-03-11 17:43 ` dpdklab
2024-03-11 17:45 ` dpdklab
2024-03-11 17:45 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:48 ` dpdklab
2024-03-11 17:48 ` dpdklab
2024-03-11 17:48 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:50 ` dpdklab
2024-03-11 17:53 ` dpdklab
2024-03-11 17:54 ` dpdklab
2024-03-11 17:55 ` dpdklab
2024-03-11 18:35 ` dpdklab
2024-03-11 18:40 ` dpdklab
2024-03-11 18:44 ` dpdklab
2024-03-11 18:49 ` dpdklab
2024-03-11 18:55 ` dpdklab
2024-03-11 23:00 ` dpdklab
2024-03-11 23:04 ` dpdklab
2024-03-11 23:08 ` dpdklab [this message]
2024-03-11 23:14 ` dpdklab
2024-03-15  1:59 ` dpdklab
2024-03-15  2:25 ` 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=65ef8ee1.0d0a0220.79caf.7e25SMTPIN_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).