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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| [GIT MASTER] 6c8aed5ab7f6dbed8e71199504fa227f5f60c6fd
Date: Mon,  5 Dec 2022 18:21:13 -0500 (EST)	[thread overview]
Message-ID: <20221205232113.1AE7019DB7@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

_Functional Testing PASS_

Branch: dpdk

6c8aed5ab7f6dbed8e71199504fa227f5f60c6fd --> 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/2


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-12-05 23:21 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 23:21 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-07 18:31 dpdklab
2022-12-07 18:27 dpdklab
2022-12-07 18:18 dpdklab
2022-12-07 18:18 dpdklab
2022-12-07 18:11 dpdklab
2022-12-07 18:03 dpdklab
2022-12-07 17:57 dpdklab
2022-12-07 17:56 dpdklab
2022-12-07 17:54 dpdklab
2022-12-07 17:30 dpdklab
2022-12-07 17:08 dpdklab
2022-12-07 17:04 dpdklab
2022-12-07 16:50 dpdklab
2022-12-07 16:48 dpdklab
2022-12-07 16:48 dpdklab
2022-12-07 16:43 dpdklab
2022-12-06  0:39 dpdklab
2022-12-06  0:39 dpdklab
2022-12-06  0:37 dpdklab
2022-12-06  0:33 dpdklab
2022-12-06  0:26 dpdklab
2022-12-06  0:23 dpdklab
2022-12-06  0:21 dpdklab
2022-12-06  0:15 dpdklab
2022-12-06  0:14 dpdklab
2022-12-06  0:14 dpdklab
2022-12-06  0:10 dpdklab
2022-12-06  0:04 dpdklab
2022-12-05 23:56 dpdklab
2022-12-05 23:56 dpdklab
2022-12-05 23:55 dpdklab
2022-12-05 23:17 dpdklab
2022-12-05 23:08 dpdklab
2022-12-05 23:02 dpdklab
2022-12-05 23:01 dpdklab
2022-12-05 22:56 dpdklab
2022-12-05 21:25 dpdklab
2022-12-05 21:25 dpdklab
2022-12-05 21:21 dpdklab
2022-12-05 21:10 dpdklab
2022-12-05 20:37 dpdklab
2022-12-05 20:31 dpdklab
2022-12-05 20:30 dpdklab
2022-12-05 20:21 dpdklab
2022-12-05 20:19 dpdklab
2022-12-05 20:13 dpdklab
2022-12-05 20:05 dpdklab
2022-12-05 20:04 dpdklab
2022-12-05 19:55 dpdklab
2022-12-05 19:48 dpdklab
2022-12-05 19:44 dpdklab
2022-12-05 19:41 dpdklab
2022-12-05 19:36 dpdklab
2022-12-05 19:30 dpdklab
2022-12-05 19:28 dpdklab
2022-12-05 19:24 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=20221205232113.1AE7019DB7@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).