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| pw135762-135765 [PATCH] [v4,4/4] baseband/fpga_5gnr_fec: c
Date: Fri, 05 Jan 2024 15:37:11 -0800 (PST)	[thread overview]
Message-ID: <659892a7.170a0220.a0da1.73c6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Friday, January 05 2024 21:15:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-05 23:37 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 23:37 dpdklab [this message]
2024-01-05 23:37 dpdklab
2024-01-05 23:38 dpdklab
2024-01-05 23:38 dpdklab
2024-01-05 23:38 dpdklab
2024-01-05 23:39 dpdklab
2024-01-05 23:44 dpdklab
2024-01-05 23:50 dpdklab
2024-01-05 23:52 dpdklab
2024-01-05 23:52 dpdklab
2024-01-05 23:58 dpdklab
2024-01-05 23:58 dpdklab
2024-01-05 23:59 dpdklab
2024-01-06  0:00 dpdklab
2024-01-06  0:01 dpdklab
2024-01-06  0:07 dpdklab
2024-01-06  0:08 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:20 dpdklab
2024-01-06  0:34 dpdklab
2024-01-06  0:35 dpdklab
2024-01-06  0:36 dpdklab
2024-01-06  0:36 dpdklab
2024-01-06  0:36 dpdklab
2024-01-06  0:36 dpdklab
2024-01-06  0:36 dpdklab
2024-01-06  0:37 dpdklab
2024-01-06  0:37 dpdklab
2024-01-06  0:37 dpdklab
2024-01-06  0:37 dpdklab
2024-01-06  0:38 dpdklab
2024-01-06  0:38 dpdklab
2024-01-06  0:38 dpdklab
2024-01-06  0:38 dpdklab
2024-01-06  0:38 dpdklab
2024-01-06  0:39 dpdklab
2024-01-06  0:39 dpdklab
2024-01-06  0:40 dpdklab
2024-01-06  0:40 dpdklab
2024-01-06  0:40 dpdklab
2024-01-06  0:40 dpdklab
2024-01-06  0:40 dpdklab
2024-01-06  0:40 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:41 dpdklab
2024-01-06  0:42 dpdklab
2024-01-06  0:42 dpdklab
2024-01-06  0:43 dpdklab
2024-01-06  0:43 dpdklab
2024-01-06  0:45 dpdklab
2024-01-06  0:52 dpdklab
2024-01-06  1:31 dpdklab
2024-01-06  1:46 dpdklab
2024-01-06  3:25 dpdklab
2024-01-06  3:55 dpdklab
2024-01-06  4:18 dpdklab
2024-01-06  7:29 dpdklab
2024-01-06  9:05 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=659892a7.170a0220.a0da1.73c6SMTPIN_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).