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| pw140238-140269 [PATCH] [v5,32/32] net/af_xdp:: replace us
Date: Tue, 21 May 2024 22:28:01 -0700 (PDT)	[thread overview]
Message-ID: <664d8261.050a0220.4fc4b.6725SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240522033009.143100-33-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, May 22 2024 03:27:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33

140238-140269 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
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.83+
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
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 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/29987/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-22  5:28 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240522033009.143100-33-stephen@networkplumber.org>
2024-05-22  3:29 ` |SUCCESS| pw140238-140269 [PATCH v5 32/32] net/af_xdp:: replace use of fixed size rte_memcpy qemudev
2024-05-22  3:34 ` qemudev
2024-05-22  3:34 ` |SUCCESS| pw140269 " checkpatch
2024-05-22  4:24 ` 0-day Robot
2024-05-22  4:36 ` |SUCCESS| pw140238-140269 [PATCH] [v5,32/32] net/af_xdp:: replace us dpdklab
2024-05-22  4:36 ` dpdklab
2024-05-22  4:36 ` dpdklab
2024-05-22  4:37 ` dpdklab
2024-05-22  4:37 ` dpdklab
2024-05-22  4:37 ` dpdklab
2024-05-22  4:37 ` dpdklab
2024-05-22  4:37 ` dpdklab
2024-05-22  4:38 ` dpdklab
2024-05-22  4:38 ` dpdklab
2024-05-22  4:38 ` dpdklab
2024-05-22  4:38 ` dpdklab
2024-05-22  4:39 ` dpdklab
2024-05-22  4:39 ` dpdklab
2024-05-22  4:39 ` dpdklab
2024-05-22  4:39 ` dpdklab
2024-05-22  4:39 ` dpdklab
2024-05-22  4:39 ` dpdklab
2024-05-22  4:39 ` dpdklab
2024-05-22  4:40 ` dpdklab
2024-05-22  4:40 ` dpdklab
2024-05-22  4:40 ` dpdklab
2024-05-22  4:40 ` dpdklab
2024-05-22  4:40 ` dpdklab
2024-05-22  4:40 ` dpdklab
2024-05-22  4:41 ` dpdklab
2024-05-22  4:41 ` dpdklab
2024-05-22  4:41 ` dpdklab
2024-05-22  4:41 ` dpdklab
2024-05-22  4:41 ` dpdklab
2024-05-22  4:41 ` dpdklab
2024-05-22  4:42 ` dpdklab
2024-05-22  4:42 ` dpdklab
2024-05-22  4:42 ` dpdklab
2024-05-22  4:43 ` dpdklab
2024-05-22  4:43 ` dpdklab
2024-05-22  4:43 ` dpdklab
2024-05-22  4:44 ` dpdklab
2024-05-22  4:44 ` dpdklab
2024-05-22  4:44 ` dpdklab
2024-05-22  4:44 ` dpdklab
2024-05-22  4:44 ` dpdklab
2024-05-22  4:45 ` dpdklab
2024-05-22  4:45 ` dpdklab
2024-05-22  4:45 ` dpdklab
2024-05-22  4:45 ` dpdklab
2024-05-22  4:45 ` dpdklab
2024-05-22  4:46 ` dpdklab
2024-05-22  4:46 ` dpdklab
2024-05-22  4:46 ` dpdklab
2024-05-22  4:46 ` dpdklab
2024-05-22  4:46 ` dpdklab
2024-05-22  4:46 ` dpdklab
2024-05-22  4:47 ` dpdklab
2024-05-22  4:47 ` dpdklab
2024-05-22  4:47 ` dpdklab
2024-05-22  4:47 ` dpdklab
2024-05-22  4:48 ` dpdklab
2024-05-22  4:48 ` dpdklab
2024-05-22  4:49 ` dpdklab
2024-05-22  4:50 ` dpdklab
2024-05-22  4:50 ` dpdklab
2024-05-22  4:50 ` dpdklab
2024-05-22  4:51 ` dpdklab
2024-05-22  4:51 ` dpdklab
2024-05-22  4:51 ` dpdklab
2024-05-22  4:52 ` dpdklab
2024-05-22  4:52 ` dpdklab
2024-05-22  4:56 ` dpdklab
2024-05-22  5:25 ` dpdklab
2024-05-22  5:26 ` dpdklab
2024-05-22  5:26 ` dpdklab
2024-05-22  5:27 ` dpdklab
2024-05-22  5:27 ` dpdklab
2024-05-22  5:28 ` dpdklab [this message]
2024-05-22  5:28 ` dpdklab
2024-05-22  5:28 ` dpdklab
2024-05-22  5:29 ` dpdklab
2024-05-22  5:30 ` dpdklab
2024-05-22  5:30 ` dpdklab
2024-05-22  5:42 ` dpdklab
2024-05-22  5:55 ` dpdklab
2024-05-22  6:20 ` dpdklab
2024-05-22  6:33 ` dpdklab
2024-05-23  6:10 ` 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=664d8261.050a0220.4fc4b.6725SMTPIN_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).