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| pw138406 [PATCH] eal: fix comment about vfio device info i
Date: Thu, 14 Mar 2024 10:21:29 -0700 (PDT)	[thread overview]
Message-ID: <65f33219.170a0220.a4eea.2ee7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314162819.16971-1-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, March 14 2024 16:28:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3

138406 --> functional testing pass

Test environment and result as below:

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


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


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

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-14 17:21 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240314162819.16971-1-stephen@networkplumber.org>
2024-03-14 16:16 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info in version.map qemudev
2024-03-14 16:21 ` qemudev
2024-03-14 16:28 ` checkpatch
2024-03-14 17:11 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info i dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:15 ` dpdklab
2024-03-14 17:16 ` dpdklab
2024-03-14 17:19 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab [this message]
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:23 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info in version.map 0-day Robot
2024-03-14 17:24 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info i dpdklab
2024-03-14 17:24 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:27 ` dpdklab
2024-03-14 17:27 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:32 ` dpdklab
2024-03-14 17:33 ` dpdklab
2024-03-14 17:33 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:56 ` dpdklab
2024-03-14 18:30 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:51 ` 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=65f33219.170a0220.a4eea.2ee7SMTPIN_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).