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| [GIT MASTER] 515e1a4f4cddd33fcb35328a73449d30a8edfaf6
Date: Mon, 22 Jan 2024 11:00:47 -0800 (PST)	[thread overview]
Message-ID: <65aebb5f.050a0220.1f3c4.5f77SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk

515e1a4f4cddd33fcb35328a73449d30a8edfaf6 --> functional testing pass

Test environment and result as below:

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


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


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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-22 19:00 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 19:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 23:38 dpdklab
2024-01-22 23:31 dpdklab
2024-01-22 18:50 dpdklab
2024-01-22  4:57 dpdklab
2024-01-22  2:50 dpdklab
2024-01-22  2:26 dpdklab
2024-01-22  2:24 dpdklab
2024-01-22  2:23 dpdklab
2024-01-22  2:23 dpdklab
2024-01-22  2:22 dpdklab
2024-01-22  2:22 dpdklab
2024-01-22  2:21 dpdklab
2024-01-22  2:20 dpdklab
2024-01-22  2:20 dpdklab
2024-01-22  2:19 dpdklab
2024-01-22  2:18 dpdklab
2024-01-22  2:16 dpdklab
2024-01-22  2:13 dpdklab
2024-01-22  2:12 dpdklab
2024-01-22  2:12 dpdklab
2024-01-22  2:12 dpdklab
2024-01-22  2:11 dpdklab
2024-01-22  2:11 dpdklab
2024-01-22  2:10 dpdklab
2024-01-22  2:10 dpdklab
2024-01-22  2:09 dpdklab
2024-01-22  2:09 dpdklab
2024-01-22  2:08 dpdklab
2024-01-22  2:07 dpdklab
2024-01-22  2:07 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:06 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:05 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:04 dpdklab
2024-01-22  2:03 dpdklab
2024-01-22  2:03 dpdklab
2024-01-22  2:03 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:02 dpdklab
2024-01-22  2:01 dpdklab
2024-01-22  2:01 dpdklab
2024-01-22  2:00 dpdklab
2024-01-22  2:00 dpdklab
2024-01-22  1:59 dpdklab
2024-01-22  1:58 dpdklab
2024-01-22  1:58 dpdklab
2024-01-20 13:28 dpdklab
2024-01-20  7:12 dpdklab
2024-01-20  6:37 dpdklab
2024-01-20  5:32 dpdklab
2024-01-20  3:20 dpdklab
2024-01-20  3:19 dpdklab
2024-01-20  3:18 dpdklab
2024-01-20  3:16 dpdklab
2024-01-20  3:15 dpdklab
2024-01-20  3:14 dpdklab
2024-01-20  3:14 dpdklab
2024-01-20  3:13 dpdklab
2024-01-20  3:13 dpdklab
2024-01-20  3:13 dpdklab
2024-01-20  3:12 dpdklab
2024-01-20  3:12 dpdklab
2024-01-20  3:10 dpdklab
2024-01-20  3:09 dpdklab
2024-01-20  3:04 dpdklab
2024-01-20  3:02 dpdklab
2024-01-20  3:00 dpdklab
2024-01-20  3:00 dpdklab
2024-01-20  3:00 dpdklab
2024-01-20  2:33 dpdklab
2024-01-20  2:32 dpdklab
2024-01-20  2:32 dpdklab
2024-01-20  2:30 dpdklab
2024-01-20  2:30 dpdklab
2024-01-20  2:29 dpdklab
2024-01-20  2:28 dpdklab
2024-01-20  2:28 dpdklab
2024-01-20  2:28 dpdklab
2024-01-20  2:27 dpdklab
2024-01-20  2:27 dpdklab
2024-01-20  2:26 dpdklab
2024-01-20  2:26 dpdklab
2024-01-20  2:26 dpdklab
2024-01-20  2:25 dpdklab
2024-01-20  2:25 dpdklab
2024-01-20  2:25 dpdklab
2024-01-20  2:22 dpdklab
2024-01-20  2:22 dpdklab
2024-01-20  2:22 dpdklab
2024-01-20  2:21 dpdklab
2024-01-20  2:21 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:20 dpdklab
2024-01-20  2:18 dpdklab
2024-01-20  2:12 dpdklab
2024-01-20  2:10 dpdklab
2024-01-20  2:10 dpdklab
2024-01-20  2:02 dpdklab
2024-01-20  2:02 dpdklab
2024-01-20  2:02 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=65aebb5f.050a0220.1f3c4.5f77SMTPIN_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).