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] 9136514c99c0b1ae9bc0d3c386d2756711b5e9ae
Date: Tue, 28 Nov 2023 04:39:29 -0800 (PST)	[thread overview]
Message-ID: <6565df81.170a0220.160b3.3dd6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-eventdev

9136514c99c0b1ae9bc0d3c386d2756711b5e9ae --> 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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-28 12:39 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 12:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-29  3:28 dpdklab
2023-11-29  1:45 dpdklab
2023-11-29  1:26 dpdklab
2023-11-29  1:23 dpdklab
2023-11-29  0:55 dpdklab
2023-11-29  0:54 dpdklab
2023-11-29  0:54 dpdklab
2023-11-29  0:54 dpdklab
2023-11-29  0:53 dpdklab
2023-11-29  0:52 dpdklab
2023-11-29  0:51 dpdklab
2023-11-29  0:51 dpdklab
2023-11-29  0:50 dpdklab
2023-11-29  0:49 dpdklab
2023-11-29  0:48 dpdklab
2023-11-29  0:46 dpdklab
2023-11-29  0:46 dpdklab
2023-11-29  0:46 dpdklab
2023-11-29  0:45 dpdklab
2023-11-29  0:45 dpdklab
2023-11-29  0:44 dpdklab
2023-11-29  0:44 dpdklab
2023-11-29  0:43 dpdklab
2023-11-29  0:43 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:42 dpdklab
2023-11-29  0:41 dpdklab
2023-11-29  0:41 dpdklab
2023-11-29  0:41 dpdklab
2023-11-29  0:41 dpdklab
2023-11-29  0:41 dpdklab
2023-11-29  0:41 dpdklab
2023-11-29  0:40 dpdklab
2023-11-29  0:40 dpdklab
2023-11-29  0:40 dpdklab
2023-11-29  0:39 dpdklab
2023-11-29  0:38 dpdklab
2023-11-29  0:38 dpdklab
2023-11-29  0:37 dpdklab
2023-11-29  0:37 dpdklab
2023-11-29  0:36 dpdklab
2023-11-29  0:36 dpdklab
2023-11-29  0:36 dpdklab
2023-11-29  0:35 dpdklab
2023-11-29  0:35 dpdklab
2023-11-29  0:34 dpdklab
2023-11-29  0:34 dpdklab
2023-11-29  0:33 dpdklab
2023-11-29  0:33 dpdklab
2023-11-29  0:32 dpdklab
2023-11-28 14:05 dpdklab
2023-11-28 13:28 dpdklab
2023-11-28 12:55 dpdklab
2023-11-28 12:55 dpdklab
2023-11-28 12:52 dpdklab
2023-11-28 12:51 dpdklab
2023-11-28 12:50 dpdklab
2023-11-28 12:48 dpdklab
2023-11-28 12:45 dpdklab
2023-11-28 12:44 dpdklab
2023-11-28 12:42 dpdklab
2023-11-28 12:38 dpdklab
2023-11-28 12:38 dpdklab
2023-11-28 12:36 dpdklab
2023-11-28 12:35 dpdklab
2023-11-28 12:35 dpdklab
2023-11-28 12:34 dpdklab
2023-11-28 12:33 dpdklab
2023-11-28 12:33 dpdklab
2023-11-28 12:33 dpdklab
2023-11-28 12:32 dpdklab
2023-11-28 12:32 dpdklab
2023-11-28 12:29 dpdklab
2023-11-28 12:28 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:26 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:23 dpdklab
2023-11-28 12:22 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=6565df81.170a0220.160b3.3dd6SMTPIN_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).