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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 31a4216a9ee3c02cf2443d533f6a491cdb25904e
Date: Thu, 21 Mar 2024 01:36:01 -0700 (PDT)	[thread overview]
Message-ID: <65fbf171.170a0220.64471.a889SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net

31a4216a9ee3c02cf2443d533f6a491cdb25904e --> 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/28576/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-21  8:36 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21  8:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-23  5:22 dpdklab
2024-03-23  4:57 dpdklab
2024-03-21 23:29 dpdklab
2024-03-21 14:56 dpdklab
2024-03-21 14:42 dpdklab
2024-03-21 12:37 dpdklab
2024-03-21 11:41 dpdklab
2024-03-21 11:39 dpdklab
2024-03-21 11:28 dpdklab
2024-03-21 11:28 dpdklab
2024-03-21 11:21 dpdklab
2024-03-21 11:16 dpdklab
2024-03-21 11:16 dpdklab
2024-03-21 11:16 dpdklab
2024-03-21 11:15 dpdklab
2024-03-21 11:14 dpdklab
2024-03-21 11:14 dpdklab
2024-03-21 11:13 dpdklab
2024-03-21 11:13 dpdklab
2024-03-21 11:13 dpdklab
2024-03-21 11:13 dpdklab
2024-03-21 11:12 dpdklab
2024-03-21 11:11 dpdklab
2024-03-21 11:09 dpdklab
2024-03-21 11:09 dpdklab
2024-03-21 11:09 dpdklab
2024-03-21 11:08 dpdklab
2024-03-21 11:01 dpdklab
2024-03-21 11:00 dpdklab
2024-03-21 11:00 dpdklab
2024-03-21 10:58 dpdklab
2024-03-21 10:57 dpdklab
2024-03-21 10:57 dpdklab
2024-03-21 10:57 dpdklab
2024-03-21 10:57 dpdklab
2024-03-21 10:56 dpdklab
2024-03-21 10:54 dpdklab
2024-03-21 10:42 dpdklab
2024-03-21 10:30 dpdklab
2024-03-21 10:26 dpdklab
2024-03-21 10:16 dpdklab
2024-03-21 10:15 dpdklab
2024-03-21 10:14 dpdklab
2024-03-21 10:14 dpdklab
2024-03-21 10:13 dpdklab
2024-03-21 10:12 dpdklab
2024-03-21 10:09 dpdklab
2024-03-21 10:09 dpdklab
2024-03-21 10:08 dpdklab
2024-03-21  8:56 dpdklab
2024-03-21  8:55 dpdklab
2024-03-21  8:51 dpdklab
2024-03-21  8:49 dpdklab
2024-03-21  8:48 dpdklab
2024-03-21  8:48 dpdklab
2024-03-21  8:47 dpdklab
2024-03-21  8:38 dpdklab
2024-03-21  8:27 dpdklab
2024-03-21  8:25 dpdklab
2024-03-21  8:20 dpdklab
2024-03-21  8:18 dpdklab
2024-03-21  8:18 dpdklab
2024-03-21  8:17 dpdklab
2024-03-21  7:51 dpdklab
2024-03-21  7:50 dpdklab
2024-03-21  7:31 dpdklab
2024-03-21  7:27 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=65fbf171.170a0220.64471.a889SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.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).