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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 7ce7d3341d7e21c2a81f2fea8e451681d7306d77
Date: Wed, 25 Dec 2024 22:38:24 -0800 (PST)	[thread overview]
Message-ID: <676cf9e0.050a0220.1de3a5.9eb8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: tags/v22.11

7ce7d3341d7e21c2a81f2fea8e451681d7306d77 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#204389

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| cmdline         |  PASS  |
+-----------------+--------+
| dynamic_queue   |  PASS  |
+-----------------+--------+
| ipv4_reassembly |  PASS  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-26  6:38 UTC|newest]

Thread overview: 152+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26  6:38 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-26 11:09 dpdklab
2024-12-26  7:40 dpdklab
2024-12-26  7:04 dpdklab
2024-12-26  7:02 dpdklab
2024-12-26  6:47 dpdklab
2024-12-26  6:42 dpdklab
2024-12-26  6:17 dpdklab
2024-12-26  6:12 dpdklab
2024-12-26  6:11 dpdklab
2024-12-26  6:09 dpdklab
2024-12-26  6:04 dpdklab
2024-12-26  6:04 dpdklab
2024-12-26  5:42 dpdklab
2024-12-25 21:36 dpdklab
2024-12-25 21:08 dpdklab
2024-12-25 17:39 dpdklab
2024-12-25 17:11 dpdklab
2024-12-25 11:19 dpdklab
2024-12-25  8:44 dpdklab
2024-12-25  7:55 dpdklab
2024-12-25  7:32 dpdklab
2024-12-25  7:32 dpdklab
2024-12-25  7:07 dpdklab
2024-12-25  6:59 dpdklab
2024-12-25  6:57 dpdklab
2024-12-25  6:56 dpdklab
2024-12-25  6:47 dpdklab
2024-12-25  6:41 dpdklab
2024-12-25  6:31 dpdklab
2024-12-25  5:53 dpdklab
2024-12-25  5:47 dpdklab
2024-12-25  5:17 dpdklab
2024-12-25  2:27 dpdklab
2024-12-25  1:50 dpdklab
2024-12-24 23:44 dpdklab
2024-12-24 23:17 dpdklab
2024-12-24 10:43 dpdklab
2024-12-24  9:12 dpdklab
2024-12-24  8:28 dpdklab
2024-12-24  8:13 dpdklab
2024-12-24  8:01 dpdklab
2024-12-24  7:52 dpdklab
2024-12-24  7:42 dpdklab
2024-12-24  7:38 dpdklab
2024-12-24  6:56 dpdklab
2024-12-24  6:42 dpdklab
2024-12-24  6:36 dpdklab
2024-12-24  5:58 dpdklab
2024-12-23  8:17 dpdklab
2024-12-23  8:16 dpdklab
2024-12-23  7:23 dpdklab
2024-12-23  7:07 dpdklab
2024-12-23  5:53 dpdklab
2024-12-23  5:36 dpdklab
2024-12-23  5:33 dpdklab
2024-12-23  5:21 dpdklab
2024-12-23  5:21 dpdklab
2024-12-23  5:19 dpdklab
2024-12-23  5:17 dpdklab
2024-12-22 10:06 dpdklab
2024-12-22  7:56 dpdklab
2024-12-22  7:42 dpdklab
2024-12-22  6:57 dpdklab
2024-12-22  6:53 dpdklab
2024-12-22  6:30 dpdklab
2024-12-22  6:09 dpdklab
2024-12-22  6:06 dpdklab
2024-12-22  6:05 dpdklab
2024-12-22  6:02 dpdklab
2024-12-22  5:50 dpdklab
2024-12-22  5:36 dpdklab
2024-12-21  8:48 dpdklab
2024-12-21  8:47 dpdklab
2024-12-21  8:46 dpdklab
2024-12-21  8:33 dpdklab
2024-12-21  7:55 dpdklab
2024-12-21  7:36 dpdklab
2024-12-21  7:26 dpdklab
2024-12-21  7:24 dpdklab
2024-12-21  7:00 dpdklab
2024-12-21  6:58 dpdklab
2024-12-21  6:46 dpdklab
2024-12-21  6:46 dpdklab
2024-12-21  6:34 dpdklab
2024-12-21  6:20 dpdklab
2024-12-21  6:10 dpdklab
2024-12-21  6:00 dpdklab
2024-12-20  9:33 dpdklab
2024-12-20  9:17 dpdklab
2024-12-20  8:39 dpdklab
2024-12-20  8:39 dpdklab
2024-12-20  8:15 dpdklab
2024-12-20  7:57 dpdklab
2024-12-20  7:44 dpdklab
2024-12-20  7:39 dpdklab
2024-12-20  7:39 dpdklab
2024-12-20  7:38 dpdklab
2024-12-20  7:30 dpdklab
2024-12-20  7:15 dpdklab
2024-12-20  7:13 dpdklab
2024-12-20  7:10 dpdklab
2024-12-20  6:50 dpdklab
2024-12-20  6:30 dpdklab
2024-12-19  8:22 dpdklab
2024-12-19  7:59 dpdklab
2024-12-19  7:16 dpdklab
2024-12-19  6:53 dpdklab
2024-12-19  6:48 dpdklab
2024-12-19  6:47 dpdklab
2024-12-19  6:35 dpdklab
2024-12-19  6:27 dpdklab
2024-12-19  6:20 dpdklab
2024-12-19  6:16 dpdklab
2024-12-19  6:14 dpdklab
2024-12-19  6:07 dpdklab
2024-12-19  5:57 dpdklab
2024-12-19  5:49 dpdklab
2024-12-19  5:47 dpdklab
2024-12-19  5:40 dpdklab
2024-12-18 12:42 dpdklab
2024-12-18 11:30 dpdklab
2024-12-18 10:28 dpdklab
2024-12-18  9:27 dpdklab
2024-12-18  9:16 dpdklab
2024-12-18  9:07 dpdklab
2024-12-18  9:06 dpdklab
2024-12-18  8:17 dpdklab
2024-12-18  8:00 dpdklab
2024-12-18  7:46 dpdklab
2024-12-18  7:44 dpdklab
2024-12-18  7:44 dpdklab
2024-12-18  7:40 dpdklab
2024-12-18  7:39 dpdklab
2024-12-18  7:36 dpdklab
2024-12-18  7:32 dpdklab
2024-12-18  6:39 dpdklab
2024-12-18  6:38 dpdklab
2024-12-18  4:02 dpdklab
2024-12-18  3:59 dpdklab
2024-12-18  3:37 dpdklab
2024-12-18  1:47 dpdklab
2024-12-18  1:45 dpdklab
2024-12-18  1:13 dpdklab
2024-12-18  0:46 dpdklab
2024-12-18  0:46 dpdklab
2024-12-18  0:23 dpdklab
2024-12-18  0:14 dpdklab
2024-12-17 23:40 dpdklab
2024-12-17 23:26 dpdklab
2024-12-17 23:10 dpdklab
2024-12-17 22:56 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=676cf9e0.050a0220.1de3a5.9eb8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).