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| pw137765-137770 [PATCH] [6/6] baseband/fpga_5gnr: don't us
Date: Fri, 01 Mar 2024 17:01:50 -0800 (PST)	[thread overview]
Message-ID: <65e27a7e.050a0220.e3514.9093SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301175842.159967-7-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, March 01 2024 17:57:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364

137765-137770 --> functional testing pass

Test environment and result as below:

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


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


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

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-02  1:01 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301175842.159967-7-stephen@networkplumber.org>
2024-03-01 18:00 ` |SUCCESS| pw137770 [PATCH 6/6] baseband/fpga_5gnr: don't use rand checkpatch
2024-03-01 19:05 ` |SUCCESS| pw137770 [PATCH 6/6] baseband/fpga_5gnr: don't use rand() 0-day Robot
2024-03-01 23:19 ` |SUCCESS| pw137765-137770 [PATCH] [6/6] baseband/fpga_5gnr: don't us dpdklab
2024-03-01 23:20 ` dpdklab
2024-03-01 23:27 ` dpdklab
2024-03-01 23:36 ` dpdklab
2024-03-01 23:41 ` dpdklab
2024-03-01 23:42 ` dpdklab
2024-03-01 23:42 ` dpdklab
2024-03-01 23:42 ` dpdklab
2024-03-01 23:43 ` dpdklab
2024-03-01 23:43 ` dpdklab
2024-03-01 23:44 ` dpdklab
2024-03-01 23:44 ` dpdklab
2024-03-01 23:45 ` dpdklab
2024-03-01 23:52 ` dpdklab
2024-03-01 23:53 ` dpdklab
2024-03-01 23:53 ` dpdklab
2024-03-01 23:55 ` dpdklab
2024-03-01 23:56 ` dpdklab
2024-03-02  0:57 ` dpdklab
2024-03-02  1:01 ` dpdklab [this message]
2024-03-02  1:06 ` dpdklab
2024-03-02  1:08 ` dpdklab
2024-03-02  2:16 ` |SUCCESS| pw137765-137770 [PATCH 6/6] baseband/fpga_5gnr: don't use rand() qemudev
2024-03-02  2:20 ` qemudev
2024-03-02  2:36 ` |SUCCESS| pw137765-137770 [PATCH] [6/6] baseband/fpga_5gnr: don't us dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:45 ` dpdklab
2024-03-02  2:45 ` dpdklab
2024-03-02  2:45 ` dpdklab
2024-03-02  2:46 ` dpdklab
2024-03-02  2:46 ` dpdklab
2024-03-02  2:47 ` dpdklab
2024-03-02  2:48 ` dpdklab
2024-03-02  2:49 ` dpdklab
2024-03-02  2:51 ` dpdklab
2024-03-02  2:51 ` dpdklab
2024-03-02  2:51 ` dpdklab
2024-03-02  2:51 ` dpdklab
2024-03-02  2:52 ` dpdklab
2024-03-02  2:52 ` dpdklab
2024-03-02  2:52 ` dpdklab
2024-03-02  2:52 ` dpdklab
2024-03-02  2:52 ` dpdklab
2024-03-02  2:53 ` dpdklab
2024-03-02  2:53 ` dpdklab
2024-03-02  2:53 ` dpdklab
2024-03-02  2:53 ` dpdklab
2024-03-02  2:54 ` dpdklab
2024-03-02  2:54 ` dpdklab
2024-03-02  2:54 ` dpdklab
2024-03-02  2:55 ` dpdklab
2024-03-02  2:55 ` dpdklab
2024-03-02  2:56 ` dpdklab
2024-03-02  2:56 ` dpdklab
2024-03-02  2:59 ` dpdklab
2024-03-02  3:01 ` dpdklab
2024-03-02  3:43 ` dpdklab
2024-03-02  3:44 ` dpdklab
2024-03-02  3:50 ` dpdklab
2024-03-02  3:50 ` dpdklab
2024-03-02  3:56 ` dpdklab
2024-03-02  3:57 ` dpdklab
2024-03-02  4:03 ` dpdklab
2024-03-02  4:05 ` dpdklab
2024-03-02  4:53 ` dpdklab
2024-03-02  5:09 ` dpdklab
2024-03-02  5:18 ` dpdklab
2024-03-03  3:49 ` dpdklab
2024-03-06  8:18 ` dpdklab
2024-03-06  9:04 ` dpdklab
2024-03-06 10:07 ` 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=65e27a7e.050a0220.e3514.9093SMTPIN_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).