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] 9836014d4c2b1b2c29948c928fd386b2944b6bcf
Date: Mon, 07 Aug 2023 18:04:52 -0700 (PDT)	[thread overview]
Message-ID: <64d194b4.9f0a0220.34db5.d5a7SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk

9836014d4c2b1b2c29948c928fd386b2944b6bcf --> 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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-08  1:04 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  1:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-08 21:48 dpdklab
2023-08-08 21:44 dpdklab
2023-08-08 21:27 dpdklab
2023-08-08 21:23 dpdklab
2023-08-08 21:12 dpdklab
2023-08-08 15:42 dpdklab
2023-08-08  2:27 dpdklab
2023-08-08  2:19 dpdklab
2023-08-08  2:12 dpdklab
2023-08-08  2:08 dpdklab
2023-08-08  2:00 dpdklab
2023-08-08  1:59 dpdklab
2023-08-08  1:23 dpdklab
2023-08-08  1:20 dpdklab
2023-08-08  1:11 dpdklab
2023-08-08  1:09 dpdklab
2023-08-08  1:09 dpdklab
2023-08-08  1:02 dpdklab
2023-08-08  1:02 dpdklab
2023-08-07 17:14 dpdklab
2023-08-07 17:07 dpdklab
2023-08-07 16:56 dpdklab
2023-08-07 16:51 dpdklab
2023-08-07 16:46 dpdklab
2023-08-07 16:42 dpdklab
2023-08-07 16:27 dpdklab
2023-08-07 16:26 dpdklab
2023-08-07 16:15 dpdklab
2023-08-07 16:15 dpdklab
2023-08-07 16:13 dpdklab
2023-08-07 16:13 dpdklab
2023-08-07 16:12 dpdklab
2023-08-07 16:11 dpdklab
2023-08-07 16:04 dpdklab
2023-08-07 15:56 dpdklab
2023-08-07 15:56 dpdklab
2023-08-07 15:53 dpdklab
2023-08-07 15:51 dpdklab
2023-08-07 15:50 dpdklab
2023-08-07 15:49 dpdklab
2023-08-07 15:36 dpdklab
2023-08-07 15:08 dpdklab
2023-08-07 14:47 dpdklab
2023-08-07  3:03 dpdklab
2023-08-07  2:34 dpdklab
2023-08-07  2:24 dpdklab
2023-08-07  2:23 dpdklab
2023-08-07  2:14 dpdklab
2023-08-07  2:09 dpdklab
2023-08-07  2:03 dpdklab
2023-08-07  1:55 dpdklab
2023-08-07  1:50 dpdklab
2023-08-07  1:46 dpdklab
2023-08-07  1:29 dpdklab
2023-08-07  1:21 dpdklab
2023-08-07  1:17 dpdklab
2023-08-07  1:13 dpdklab
2023-08-07  1:13 dpdklab
2023-08-07  1:13 dpdklab
2023-08-07  1:12 dpdklab
2023-08-07  1:12 dpdklab
2023-08-07  1:12 dpdklab
2023-08-07  1:11 dpdklab
2023-08-06  2:29 dpdklab
2023-08-06  2:18 dpdklab
2023-08-06  2:15 dpdklab
2023-08-06  2:14 dpdklab
2023-08-06  2:13 dpdklab
2023-08-06  2:12 dpdklab
2023-08-06  2:09 dpdklab
2023-08-06  1:47 dpdklab
2023-08-06  1:41 dpdklab
2023-08-06  1:30 dpdklab
2023-08-06  1:21 dpdklab
2023-08-06  1:19 dpdklab
2023-08-06  1:18 dpdklab
2023-08-06  1:18 dpdklab
2023-08-06  1:18 dpdklab
2023-08-06  1:18 dpdklab
2023-08-06  1:17 dpdklab
2023-08-06  1:17 dpdklab
2023-08-05  2:45 dpdklab
2023-08-05  2:45 dpdklab
2023-08-05  2:45 dpdklab
2023-08-05  2:42 dpdklab
2023-08-05  2:30 dpdklab
2023-08-05  2:29 dpdklab
2023-08-05  2:18 dpdklab
2023-08-05  2:16 dpdklab
2023-08-05  1:44 dpdklab
2023-08-05  1:37 dpdklab
2023-08-05  1:33 dpdklab
2023-08-05  1:25 dpdklab
2023-08-05  1:19 dpdklab
2023-08-05  1:13 dpdklab
2023-08-05  1:13 dpdklab
2023-08-05  1:13 dpdklab
2023-08-05  1:13 dpdklab
2023-08-05  1:13 dpdklab
2023-08-05  1:12 dpdklab
2023-08-05  1:11 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=64d194b4.9f0a0220.34db5.d5a7SMTPIN_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).