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] 340c178977a29d2bffa4e43122207ce3a02be7ee
Date: Mon, 23 Dec 2024 21:30:41 -0800 (PST)	[thread overview]
Message-ID: <676a4701.050a0220.b4147.de80SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: tags/v21.11

340c178977a29d2bffa4e43122207ce3a02be7ee --> testing pass

Upstream job id: Template-DTS-Pipeline#204148

Test environment and result as below:

+--------------------+----------------------+
|    Environment     | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS                 |
+--------------------+----------------------+


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-24  5:30 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24  5:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-25  7:10 dpdklab
2024-12-25  6:35 dpdklab
2024-12-25  3:01 dpdklab
2024-12-25  1:59 dpdklab
2024-12-24 23:08 dpdklab
2024-12-24 22:03 dpdklab
2024-12-24  9:03 dpdklab
2024-12-24  7:33 dpdklab
2024-12-24  7:28 dpdklab
2024-12-24  7:28 dpdklab
2024-12-24  6:34 dpdklab
2024-12-24  5:42 dpdklab
2024-12-24  5:37 dpdklab
2024-12-24  5:27 dpdklab
2024-12-23  8:19 dpdklab
2024-12-23  8:10 dpdklab
2024-12-23  8:07 dpdklab
2024-12-23  7:30 dpdklab
2024-12-23  7:09 dpdklab
2024-12-23  7:08 dpdklab
2024-12-23  6:36 dpdklab
2024-12-23  6:29 dpdklab
2024-12-23  6:26 dpdklab
2024-12-23  5:55 dpdklab
2024-12-22  7:53 dpdklab
2024-12-22  7:52 dpdklab
2024-12-22  7:31 dpdklab
2024-12-22  7:29 dpdklab
2024-12-22  7:22 dpdklab
2024-12-22  7:10 dpdklab
2024-12-22  6:39 dpdklab
2024-12-22  6:37 dpdklab
2024-12-22  6:30 dpdklab
2024-12-22  6:04 dpdklab
2024-12-22  5:51 dpdklab
2024-12-21  9:29 dpdklab
2024-12-21  9:12 dpdklab
2024-12-21  9:03 dpdklab
2024-12-21  8:49 dpdklab
2024-12-21  8:28 dpdklab
2024-12-21  6:48 dpdklab
2024-12-21  6:23 dpdklab
2024-12-21  6:03 dpdklab
2024-12-21  5:58 dpdklab
2024-12-21  5:45 dpdklab
2024-12-21  5:36 dpdklab
2024-12-20 10:37 dpdklab
2024-12-20 10:26 dpdklab
2024-12-20  9:34 dpdklab
2024-12-20  9:12 dpdklab
2024-12-20  8:28 dpdklab
2024-12-20  8:00 dpdklab
2024-12-20  7:27 dpdklab
2024-12-20  7:05 dpdklab
2024-12-20  7:03 dpdklab
2024-12-20  6:56 dpdklab
2024-12-20  6:41 dpdklab
2024-12-20  6:35 dpdklab
2024-12-20  6:22 dpdklab
2024-12-20  6:15 dpdklab
2024-12-19  8:20 dpdklab
2024-12-19  8:19 dpdklab
2024-12-19  8:19 dpdklab
2024-12-19  8:03 dpdklab
2024-12-19  8:01 dpdklab
2024-12-19  7:55 dpdklab
2024-12-19  7:21 dpdklab
2024-12-19  6:58 dpdklab
2024-12-19  6:33 dpdklab
2024-12-19  6:12 dpdklab
2024-12-19  5:39 dpdklab
2024-12-19  5:35 dpdklab
2024-12-19  5:34 dpdklab
2024-12-18 10:05 dpdklab
2024-12-18 10:04 dpdklab
2024-12-18 10:04 dpdklab
2024-12-18  9:59 dpdklab
2024-12-18  9:52 dpdklab
2024-12-18  9:36 dpdklab
2024-12-18  9:24 dpdklab
2024-12-18  9:04 dpdklab
2024-12-18  8:59 dpdklab
2024-12-18  8:56 dpdklab
2024-12-18  8:29 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=676a4701.050a0220.b4147.de80SMTPIN_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).