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] a13d7d07005a0bd0b37b102b92483d0372e5c04a
Date: Mon, 14 Aug 2023 17:01:06 -0700 (PDT)	[thread overview]
Message-ID: <64dac042.050a0220.399f0.f774SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net

a13d7d07005a0bd0b37b102b92483d0372e5c04a --> 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/4


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


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-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/tarballs/25816/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-15  0:01 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  0:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15  0:22 dpdklab
2023-08-15  0:05 dpdklab
2023-08-14 23:56 dpdklab
2023-08-14 23:45 dpdklab
2023-08-14 20:00 dpdklab
2023-08-14 20:00 dpdklab
2023-08-14 19:10 dpdklab
2023-08-14 19:08 dpdklab
2023-08-14 18:52 dpdklab
2023-08-14 18:51 dpdklab
2023-08-14 18:48 dpdklab
2023-08-14 18:48 dpdklab
2023-08-14 18:47 dpdklab
2023-08-14 18:47 dpdklab
2023-08-14 18:46 dpdklab
2023-08-14 18:46 dpdklab
2023-08-14 18:40 dpdklab
2023-08-14 18:40 dpdklab
2023-08-14 18:38 dpdklab
2023-08-14 18:37 dpdklab
2023-08-14 18:37 dpdklab
2023-08-14 18:37 dpdklab
2023-08-14 18:36 dpdklab
2023-08-14 18:36 dpdklab
2023-08-14 18:36 dpdklab
2023-08-14 18:36 dpdklab
2023-08-14 18:35 dpdklab
2023-08-14 18:34 dpdklab
2023-08-14 18:34 dpdklab
2023-08-14 18:33 dpdklab
2023-08-14 18:33 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:32 dpdklab
2023-08-14 18:31 dpdklab
2023-08-14 18:31 dpdklab
2023-08-14 18:31 dpdklab
2023-08-14 18:31 dpdklab
2023-08-14 18:31 dpdklab
2023-08-14 18:31 dpdklab
2023-08-14 18:30 dpdklab
2023-08-14 18:30 dpdklab
2023-08-14 18:30 dpdklab
2023-08-14 18:30 dpdklab
2023-08-14 18:29 dpdklab
2023-08-14 18:29 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=64dac042.050a0220.399f0.f774SMTPIN_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).