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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 3c464365f8c881863ca911631c0ab0aa18d62032
Date: Fri, 22 Mar 2024 14:18:18 -0700 (PDT)	[thread overview]
Message-ID: <65fdf59a.050a0220.f4138.08d0SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-crypto

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


Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28599/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-22 21:18 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 21:18 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-24 10:54 dpdklab
2024-03-24 10:18 dpdklab
2024-03-23  1:41 dpdklab
2024-03-22 23:01 dpdklab
2024-03-22 22:43 dpdklab
2024-03-22 22:34 dpdklab
2024-03-22 22:31 dpdklab
2024-03-22 22:30 dpdklab
2024-03-22 22:28 dpdklab
2024-03-22 22:27 dpdklab
2024-03-22 22:27 dpdklab
2024-03-22 22:24 dpdklab
2024-03-22 22:24 dpdklab
2024-03-22 22:23 dpdklab
2024-03-22 22:08 dpdklab
2024-03-22 22:07 dpdklab
2024-03-22 22:07 dpdklab
2024-03-22 22:07 dpdklab
2024-03-22 22:06 dpdklab
2024-03-22 22:06 dpdklab
2024-03-22 22:05 dpdklab
2024-03-22 22:05 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:02 dpdklab
2024-03-22 22:01 dpdklab
2024-03-22 22:00 dpdklab
2024-03-22 21:52 dpdklab
2024-03-22 21:51 dpdklab
2024-03-22 21:51 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:49 dpdklab
2024-03-22 21:49 dpdklab
2024-03-22 21:46 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:44 dpdklab
2024-03-22 21:44 dpdklab
2024-03-22 21:44 dpdklab
2024-03-22 21:41 dpdklab
2024-03-22 21:32 dpdklab
2024-03-22 21:32 dpdklab
2024-03-22 21:32 dpdklab
2024-03-22 21:31 dpdklab
2024-03-22 21:31 dpdklab
2024-03-22 21:25 dpdklab
2024-03-22 21:19 dpdklab
2024-03-22 21:04 dpdklab
2024-03-22 21:04 dpdklab
2024-03-22 21:03 dpdklab
2024-03-22 21:03 dpdklab
2024-03-22 21:02 dpdklab
2024-03-22 20:56 dpdklab
2024-03-22 20:55 dpdklab
2024-03-22 20:50 dpdklab
2024-03-22 20:45 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=65fdf59a.050a0220.f4138.08d0SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@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).