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, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] b36f9f53f05a54424b831c8acfec3da79c53c696
Date: Tue, 28 May 2024 10:11:50 -0700 (PDT)	[thread overview]
Message-ID: <66561056.050a0220.4a210.129fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-eventdev

b36f9f53f05a54424b831c8acfec3da79c53c696 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
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: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
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/tarballs/29232/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-05-28 17:12 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 17:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-30  3:40 dpdklab
2024-05-30  3:40 dpdklab
2024-05-30  3:29 dpdklab
2024-05-28 19:41 dpdklab
2024-05-28 18:16 dpdklab
2024-05-28 18:01 dpdklab
2024-05-28 17:41 dpdklab
2024-05-28 17:36 dpdklab
2024-05-28 17:25 dpdklab
2024-05-28 17:24 dpdklab
2024-05-28 17:23 dpdklab
2024-05-28 17:23 dpdklab
2024-05-28 17:22 dpdklab
2024-05-28 17:21 dpdklab
2024-05-28 17:21 dpdklab
2024-05-28 17:20 dpdklab
2024-05-28 17:19 dpdklab
2024-05-28 17:19 dpdklab
2024-05-28 17:18 dpdklab
2024-05-28 17:15 dpdklab
2024-05-28 17:14 dpdklab
2024-05-28 17:14 dpdklab
2024-05-28 17:14 dpdklab
2024-05-28 17:14 dpdklab
2024-05-28 17:13 dpdklab
2024-05-28 17:13 dpdklab
2024-05-28 17:13 dpdklab
2024-05-28 17:13 dpdklab
2024-05-28 17:13 dpdklab
2024-05-28 17:13 dpdklab
2024-05-28 17:13 dpdklab
2024-05-28 17:12 dpdklab
2024-05-28 17:12 dpdklab
2024-05-28 17:12 dpdklab
2024-05-28 17:12 dpdklab
2024-05-28 17:12 dpdklab
2024-05-28 17:11 dpdklab
2024-05-28 17:11 dpdklab
2024-05-28 17:11 dpdklab
2024-05-28 17:11 dpdklab
2024-05-28 17:11 dpdklab
2024-05-28 17:11 dpdklab
2024-05-28 17:10 dpdklab
2024-05-28 17:10 dpdklab
2024-05-28 17:10 dpdklab
2024-05-28 17:10 dpdklab
2024-05-28 17:10 dpdklab
2024-05-28 17:10 dpdklab
2024-05-28 17:09 dpdklab
2024-05-28 17:09 dpdklab
2024-05-28 17:09 dpdklab
2024-05-28 17:08 dpdklab
2024-05-28 17:08 dpdklab
2024-05-28 17:08 dpdklab
2024-05-28 17:08 dpdklab
2024-05-28 17:08 dpdklab
2024-05-28 17:08 dpdklab
2024-05-28 17:07 dpdklab
2024-05-28 17:07 dpdklab
2024-05-28 17:07 dpdklab
2024-05-28 17:06 dpdklab
2024-05-28 17:06 dpdklab
2024-05-28 17:06 dpdklab
2024-05-28 17:06 dpdklab
2024-05-28 17:06 dpdklab
2024-05-28 17:05 dpdklab
2024-05-28 17:05 dpdklab
2024-05-28 17:05 dpdklab
2024-05-28 17:05 dpdklab
2024-05-28 17:05 dpdklab
2024-05-28 17:05 dpdklab
2024-05-28 17:04 dpdklab
2024-05-28 17:04 dpdklab
2024-05-28 17:03 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=66561056.050a0220.4a210.129fSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=jerinj@marvell.com \
    --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).