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| pw139761-139769 [PATCH] [v10,9/9] net/tap: update document
Date: Sat, 04 May 2024 06:52:46 -0700 (PDT)	[thread overview]
Message-ID: <66363dae.050a0220.3ea56.ee9aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240501161403.114658-10-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, May 01 2024 16:12:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139761-139769 --> functional testing pass

Test environment and result as below:

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


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


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

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-04 13:52 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240501161403.114658-10-stephen@networkplumber.org>
2024-05-01 15:50 ` |SUCCESS| pw139761-139769 [PATCH v10 9/9] net/tap: update documentation qemudev
2024-05-01 15:54 ` qemudev
2024-05-01 17:03 ` |SUCCESS| pw139769 " 0-day Robot
2024-05-01 17:31 ` |SUCCESS| pw139761-139769 [PATCH] [v10,9/9] net/tap: update document dpdklab
2024-05-01 17:32 ` dpdklab
2024-05-01 17:32 ` dpdklab
2024-05-01 17:33 ` dpdklab
2024-05-01 17:34 ` dpdklab
2024-05-01 17:36 ` dpdklab
2024-05-01 17:45 ` dpdklab
2024-05-01 17:46 ` dpdklab
2024-05-01 17:47 ` dpdklab
2024-05-01 17:49 ` dpdklab
2024-05-01 17:50 ` dpdklab
2024-05-01 17:51 ` dpdklab
2024-05-01 17:51 ` dpdklab
2024-05-01 17:51 ` dpdklab
2024-05-01 17:52 ` dpdklab
2024-05-01 17:52 ` dpdklab
2024-05-01 17:52 ` dpdklab
2024-05-01 17:53 ` dpdklab
2024-05-01 17:53 ` dpdklab
2024-05-01 17:54 ` dpdklab
2024-05-01 17:55 ` dpdklab
2024-05-01 17:56 ` dpdklab
2024-05-01 17:56 ` dpdklab
2024-05-01 17:56 ` dpdklab
2024-05-01 17:57 ` dpdklab
2024-05-01 17:57 ` dpdklab
2024-05-01 17:58 ` dpdklab
2024-05-01 17:58 ` dpdklab
2024-05-01 17:58 ` dpdklab
2024-05-01 17:59 ` dpdklab
2024-05-01 17:59 ` dpdklab
2024-05-01 17:59 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:01 ` dpdklab
2024-05-01 18:01 ` dpdklab
2024-05-01 18:02 ` dpdklab
2024-05-01 18:02 ` dpdklab
2024-05-01 18:02 ` dpdklab
2024-05-01 18:03 ` dpdklab
2024-05-01 18:03 ` dpdklab
2024-05-01 18:03 ` dpdklab
2024-05-01 18:04 ` dpdklab
2024-05-01 18:05 ` dpdklab
2024-05-01 18:05 ` dpdklab
2024-05-01 18:05 ` dpdklab
2024-05-01 18:06 ` dpdklab
2024-05-01 18:06 ` dpdklab
2024-05-01 18:06 ` dpdklab
2024-05-01 18:07 ` dpdklab
2024-05-01 18:07 ` dpdklab
2024-05-01 18:07 ` dpdklab
2024-05-01 18:08 ` dpdklab
2024-05-01 18:08 ` dpdklab
2024-05-01 18:08 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:14 ` dpdklab
2024-05-01 18:14 ` dpdklab
2024-05-01 18:17 ` dpdklab
2024-05-01 18:17 ` dpdklab
2024-05-01 18:21 ` dpdklab
2024-05-01 18:25 ` dpdklab
2024-05-01 18:34 ` dpdklab
2024-05-01 18:35 ` dpdklab
2024-05-01 19:06 ` dpdklab
2024-05-01 19:08 ` dpdklab
2024-05-01 19:12 ` dpdklab
2024-05-04  0:42 ` dpdklab
2024-05-04 13:40 ` dpdklab
2024-05-04 13:44 ` dpdklab
2024-05-04 13:48 ` dpdklab
2024-05-04 13:52 ` dpdklab [this message]
2024-05-04 14:27 ` dpdklab
2024-05-06  5:56 ` 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=66363dae.050a0220.3ea56.ee9aSMTPIN_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).